Erlang/OTP系统文档：版本12.1弃用功能

需积分: 5 7 浏览量更新于2024-07-09 收藏 1.36MB PDF 举报

"otp-system-documentation.pdf - Erlang/OTP系统文档" 本文档是Erlang/OTP系统的官方文档，由Ericsson AB版权所有，版本为12.1，更新日期为2021年9月21日。此文档遵循Apache License 2.0授权协议，用户在符合该协议条款的情况下可以使用。文档中明确指出，软件按“原样”（AS IS）基础分发，不提供任何形式的明示或暗示保修。文档的主要内容之一是关于弃用功能的列表，这是Erlang/OTP系统维护和升级策略的重要组成部分。弃用通常意味着这些功能将在未来的版本中被移除，鼓励开发者转向推荐的替代方案。详细介绍了从OTP 24版本开始的一些弃用变化。 1.1章节着重于弃用信息，1.1.1小节引入了弃用功能的概念，并引导读者查阅支持、兼容性、弃用和移除的策略文档，以获取更全面的背景知识。 1.1.2小节具体提到了OTP 24版本的弃用特性，其中提到了Erlang分布不再支持大型节点容器。这意味着在新版本中，与之前版本相比，Erlang节点之间的通信方式可能有所改变，不再支持某些特定的大数据传输能力。这可能会对依赖此功能的代码造成影响，开发者需要按照文档的指导进行代码迁移，以确保向后兼容和系统的稳定运行。 Erlang/OTP是一个用于构建高度并发、容错且易于并行处理的系统平台，尤其适用于电信、实时系统等领域。其强大的分布式计算能力和故障恢复机制使得它在高可用性系统设计中占据重要地位。OTP（Open Telephony Platform）提供了许多库和设计模式，帮助开发者实现可靠的并发程序。弃用功能是软件演进的一部分，Erlang/OTP团队通过这种方式推动语言和库的现代化，提高效率并减少潜在的问题。对于开发者来说，及时了解和应对弃用功能，是保持系统最新和优化性能的关键步骤。通过阅读此文档，开发者可以了解到当前版本的更新内容，以及如何准备未来的版本升级，以确保代码的质量和兼容性。

2.2Building and Installing Erlang/OTP

2.2.4 How to Build and Install Erlang/OTP

The following instructions are for building the released source tar ball.

The variable $ERL_TOP will be mentioned a lot of times. It refers to the top directory in the source tree. More

information about $ERL_TOP can be found in the make and $ERL_TOP section below.

Unpacking

Start by unpacking the Erlang/OTP distribution file with your GNU compatible TAR program.

$ tar -zxf otp_src_24.1.tar.gz # Assuming bash/sh

Now change directory into the base directory and set the $ERL_TOP variable.

$ cd otp_src_24.1

$ export ERL_TOP=`pwd` # Assuming bash/sh

Conﬁguring

Run the following commands to configure the build:

$ ./configure [ options ]

By default, Erlang/OTP release will be installed in /usr/local/{bin,lib/erlang}. If you for instance don't

have the permission to install in the standard location, you can install Erlang/OTP somewhere else. For example, to

install in /opt/erlang/24.1/{bin,lib/erlang}, use the --prefix=/opt/erlang/24.1 option.

On some platforms Perl may behave strangely if certain locales are set. If you get errors when building, try setting

the LANG variable:

$ export LANG=C # Assuming bash/sh

Building

Build the Erlang/OTP release.

$ make

Testing

Before installation you should test whether your build is working properly by running our smoke test. The smoke test

is a subset of the complete Erlang/OTP test suites. First you will need to build and release the test suites.

$ make release_tests

This creates an additional folder in $ERL_TOP/release called tests. Now, it's time to start the smoke test.

$ cd release/tests/test_server

$ $ERL_TOP/bin/erl -s ts install -s ts smoke_test batch -s init stop

To verify that everything is ok you should open $ERL_TOP/release/tests/test_server/index.html

in your web browser and make sure that there are zero failed test cases.

Note:

On builds without crypto, ssl and ssh there is a failed test case for undefined functions. Verify that the failed

test case log only shows calls to skipped applications.

2.2Building and Installing Erlang/OTP

Installing

You are now ready to install the Erlang/OTP release! The following command will install the release on your system.

$ make install

Running

You should now have a working release of Erlang/OTP! Jump to System Principles for instructions on running Erlang/

OTP.

How to Build the Documentation

Make sure you're in the top directory in the source tree.

$ cd $ERL_TOP

If you have just built Erlang/OTP in the current source tree, you have already ran configure and do not need to

do this again; otherwise, run configure.

$ ./configure [Configure Args]

When building the documentation you need a full Erlang/OTP-24.1 system in the $PATH.

$ export PATH=$ERL_TOP/bin:$PATH # Assuming bash/sh

For the FOP print formatter, two steps must be taken:

• Adding the location of your installation of fop in $FOP_HOME.

$ export FOP_HOME=/path/to/fop/dir # Assuming bash/sh

• Adding the fop script (in $FOP_HOME) to your $PATH, either by adding $FOP_HOME to $PATH, or by copying

the fop script to a directory already in your $PATH.

Build the documentation.

$ make docs

It is possible to limit which types of documentation is build by passing the DOC_TARGETS environment variable to

make docs. The currently available types are: html, pdf, man and chunks. Example:

$ make docs DOC_TARGETS=chunks

Build Issues

We have sometimes experienced problems with Oracle's java running out of memory when running fop. Increasing

the amount of memory available as follows has in our case solved the problem.

$ export FOP_OPTS="-Xmx<Installed amount of RAM in MB>m"

More information can be found at

• http://xmlgraphics.apache.org/fop/0.95/running.html#memory.

How to Install the Documentation

The documentation can be installed either using the install-docs target, or using the release_docs target.

• If you have installed Erlang/OTP using the install target, install the documentation using the install-

docs target. Install locations determined by configure will be used. $DESTDIR can be used the same way

as when doing make install.

2.2Building and Installing Erlang/OTP

$ make install-docs

• If you have installed Erlang/OTP using the release target, install the documentation using the release_docs

target. You typically want to use the same RELEASE_ROOT as when invoking make release.

$ make release_docs RELEASE_ROOT=<release dir>

It is possible to limit which types of documentation is released using the same DOC_TARGETS environment variable

as when building documentation.

Accessing the Documentation

After installation you can access the documentation by

• Reading man pages. Make sure that erl is referring to the installed version. For example /usr/local/bin/

erl. Try viewing at the man page for Mnesia

$ erl -man mnesia

• Browsing the html pages by loading the page /usr/local/lib/erlang/doc/erlang/index.html or

<BaseDir>/lib/erlang/doc/erlang/index.html if the prefix option has been used.

• Read the embedded documentation by using the built-in shell functions h/1,2,3 or ht/1,2,3.

How to Install the Pre-formatted Documentation

Pre-formatted html documentation and man pages can be downloaded from

• http://www.erlang.org/download.html.

Extract the html archive in the installation directory.

$ cd <ReleaseDir>

$ tar -zxf otp_html_24.1.tar.gz

For erl -man <page> to work the Unix manual pages have to be installed in the same way, i.e.

$ cd <ReleaseDir>

$ tar -zxf otp_man_24.1.tar.gz

Where <ReleaseDir> is

• <PrefixDir>/lib/erlang if you have installed Erlang/OTP using make install.

• $DESTDIR<PrefixDir>/lib/erlang if you have installed Erlang/OTP using make install

DESTDIR=<TmpInstallDir>.

• RELEASE_ROOT if you have installed using make release RELEASE_ROOT=<ReleaseDir>.

2.2.5 Advanced conﬁguration and build of Erlang/OTP

If you want to tailor your Erlang/OTP build and installation, please read on for detailed information about the individual

steps.

make and $ERL_TOP

All the makefiles in the entire directory tree use the environment variable ERL_TOP to find the absolute path of the

installation. The configure script will figure this out and set it in the top level Makefile (which, when building, it

will pass on). However, when developing it is sometimes convenient to be able to run make in a subdirectory. To do

this you must set the ERL_TOP variable before you run make.

For example, assume your GNU make program is called make and you want to rebuild the application STDLIB, then

you could do:

2.2Building and Installing Erlang/OTP

$ cd lib/stdlib; env ERL_TOP=<Dir> make

where <Dir> would be what you find ERL_TOP is set to in the top level Makefile.

otp_build vs conﬁgure/make

Building Erlang/OTP can be done either by using the $ERL_TOP/otp_build script, or by invoking $ERL_TOP/

configure and make directly. Building using otp_build is easier since it involves fewer steps, but the

otp_build build procedure is not as flexible as the configure/make build procedure. The binary releases for

Windows that we deliver are built using otp_build.

Conﬁguring

The configure script is created by the GNU autoconf utility, which checks for system specific features and then creates

a number of makefiles.

The configure script allows you to customize a number of parameters; type ./configure --help or ./

configure --help=recursive for details. ./configure --help=recursive will give help for all

configure scripts in all applications.

One of the things you can specify is where Erlang/OTP should be installed. By default Erlang/OTP will be installed in

/usr/local/{bin,lib/erlang}. To keep the same structure but install in a different place, <Dir> say, use

the --prefix argument like this: ./configure --prefix=<Dir>.

Some of the available configure options are:

• --prefix=PATH - Specify installation prefix.

• --disable-parallel-configure - Disable parallel execution of configure scripts (parallel

execution is enabled by default)

• --{enable,disable}-jit - Force enabling or disabling of the JIT.

• --{enable,disable}-kernel-poll - Kernel poll support (enabled by default if possible)

• --enable-m64-build - Build 64-bit binaries using the -m64 flag to (g)cc

• --enable-m32-build - Build 32-bit binaries using the -m32 flag to (g)cc

• --{enable,disable}-pie - Build position independent executable binaries.

• --with-assumed-cache-line-size=SIZE - Set assumed cache-line size in bytes. Default is 64. Valid

values are powers of two between and including 16 and 8192. The runtime system use this value in order to

try to avoid false sharing. A too large value wastes memory. A to small value will increase the amount of false

sharing.

• --{with,without}-termcap - termcap (without implies that only the old Erlang shell can be used)

• --with-javac=JAVAC - Specify Java compiler to use

• --{with,without}-javac - Java compiler (without implies that the jinterface application won't be

built)

• --{enable,disable}-builtin-zlib - Use the built-in source for zlib.

• --{enable,disable}-dynamic-ssl-lib - Enable or disable dynamic OpenSSL libraries when

linking the crypto NIF. By default dynamic linking is done unless it does not work or is if it is a Windows

system.

• --{with,without}-ssl - OpenSSL (without implies that the crypto, ssh, and ssl won't be built)

• --with-ssl=PATH - Specify base location of OpenSSL include and lib directories.

• --with-ssl-incl=PATH - Specify base location of OpenSSL include directory (if different than base

location specified by --with-ssl=PATH).

• --with-ssl-zlib=PATH - Path to static zlib library to link the crypto NIF with. This zlib library is most

often not necessary but might be needed in order to link the NIF in some cases.

2.2Building and Installing Erlang/OTP

• --with-ssl-lib-subdir=RELATIVE_PATH - Specify extra OpenSSL lib sub-directory to search in

(relative to base directory).

• --with-ssl-rpath=yes|no|PATHS - Runtime library path for OpenSSL. Default is yes, which equates

to a number of standard locations. If no, then no runtime library paths will be used. Anything else should be a

comma or colon separated list of paths.

• --with-libatomic_ops=PATH - Use the libatomic_ops library for atomic memory accesses. If

configure should inform you about no native atomic implementation available, you typically want to try

using the libatomic_ops library. It can be downloaded from https://github.com/ivmai/libatomic_ops/.

• --disable-smp-require-native-atomics - By default configure will fail if an SMP runtime

system is about to be built, and no implementation for native atomic memory accesses can be found. If

this happens, you are encouraged to find a native atomic implementation that can be used, e.g., using

libatomic_ops, but by passing --disable-smp-require-native-atomics you can build using a

fallback implementation based on mutexes or spinlocks. Performance of the SMP runtime system will however

suffer immensely without an implementation for native atomic memory accesses.

• --enable-static-{nifs,drivers} - To allow usage of nifs and drivers on OSs that do not

support dynamic linking of libraries it is possible to statically link nifs and drivers with the main Erlang

VM binary. This is done by passing a comma separated list to the archives that you want to statically link.

e.g. --enable-static-nifs=/home/$USER/my_nif.a. The path has to be absolute and the

name of the archive has to be the same as the module, i.e. my_nif in the example above. This is also true

for drivers, but then it is the driver name that has to be the same as the filename. You also have to define

STATIC_ERLANG_{NIF,DRIVER} when compiling the .o files for the nif/driver. If your nif/driver depends

on some other dynamic library, you now have to link that to the Erlang VM binary. This is easily achieved by

passing LIBS=-llibname to configure.

• --without-$app - By default all applications in Erlang/OTP will be included in a release. If this is not

wanted it is possible to specify that Erlang/OTP should be compiled without one or more applications, i.e. --

without-wx. There is no automatic dependency handling between applications. If you disable an application

that another application depends on, you also have to disable the dependant application.

• --enable-gettimeofday-as-os-system-time - Force usage of gettimeofday() for OS system

time.

• --enable-prefer-elapsed-monotonic-time-during-suspend - Prefer an OS monotonic time

source with elapsed time during suspend.

• --disable-prefer-elapsed-monotonic-time-during-suspend - Do not prefer an OS

monotonic time source with elapsed time during suspend.

• --with-clock-resolution=high|low - Try to find clock sources for OS system time, and OS

monotonic time with higher or lower resolution than chosen by default. Note that both alternatives may have a

negative impact on the performance and scalability compared to the default clock sources chosen.

• --disable-saved-compile-time - Disable saving of compile date and time in the emulator binary.

If you or your system has special requirements please read the Makefile for additional configuration information.

Important Variables Inspected by conﬁgure

Compiler and Linker

• CC - C compiler.

• CFLAGS - C compiler flags. Defaults to "-g -O2". If you set it, these will be removed.

• STATIC_CFLAGS - Static C compiler flags.

• CFLAG_RUNTIME_LIBRARY_PATH - This flag should set runtime library search path for the shared libraries.

Note that this actually is a linker flag, but it needs to be passed via the compiler.

• CPP - C pre-processor.

• CPPFLAGS - C pre-processor flags.

剩余388页未读，继续阅读

CupidoZ

粉丝: 2577
资源: 7

Erlang/OTP系统文档：版本12.1弃用功能

otp-OTP-20.0.tar.gz

er-lang-otp-win64-24.0.7z

OTP-638D2_SW.pdf

otp-win64-21.3.exe rabbitmq-server-3.11.2.exe

rabbit mq windows64rabbitmq-server-3.12.4.exe otp-win64-26.0.ex

PLDSEC_OTP-V1.0.0.apk.1

otp-win64-25.3.exe

otp-win64-25.0.zip

otp-win32-25.3.exe

otp-win64-27.1.exe

最新资源