Documentation

Environment

Set the environment up as usual:

Set the ERL_TOP environment variable:

cd otp
export ERL_TOP=`pwd`

Also, set a destination path for the documentation:

export TESTROOT=<path>

The repository does not contain a generated configure file, so it must be generated like this:

./otp_build autoconf

before configure can be run. When the configure files have been generated, you can build in the usual way as described in the README file. Briefly:

./configure
make

If you are building in your own local directory, you might want to supply a “—prefix=” argument for ./configure.

Build the documentation

To build the complete documentation for all applications, build it from the top:

make release_docs

If only you want to build only the documentation for a specific application, you must build erl_docgen first. Enter the erl_docgen directory and generate the necessary files:

cd $ERL_TOP/lib/erl_docgen
make release_docs

Then enter the directory for the specific application directory, and build its documentation:

cd $ERL_TOP/lib/<application>
make release_docs

This will generate the application’s documentation in three formats: UNIX-style man-page format, HTML, and PDF for the corresponding chapter in the Erlang/OTP Reference manual.