Automatically generating Erlang/OTP .app and .rel files using GNU Autoconf

A user of the GNU Autotools (Autoconf and Automake) with Erlang/OTP has recently asked me about a way to automatically generate the .app (application resource) files and .rel (release resource) files for an Erlang/OTP application. This is a perfect occasion to present the ideas that Ruslan Babayev had on the subject, which I promised to publish back in Sep. 2006. I am "only" 18 months late! (^_^);

As for now, Automake provides no help to generate those files. This is Autoconf's job. What Autoconf can do is help you avoid the manual duplication of information between several files, and help you synchronize the content of the .app and .rel files with the state of your system and your Erlang/OTP installation. The trick is to let Autoconf generate parts of the .app and .rel files for you.

To let Autoconf substitute parts of those files, first add their names into the AC_CONFIG_FILES macro call, in your file:

AC_CONFIG_FILES([... sample.rel])

Then, name your files with extensions and, e.g. and, as the configure script will generate from and sample.rel from Your and files should contain variables to substitute enclosed with @...@.

For instance, a file could be:

{application, @PACKAGE@, [{description, "Sample Erlang server"}, {vsn, "@VERSION@"}, {modules, [sample_app, sample_sup, sample_server]}, {registered, [sample_sup, sample_server]}, {applications, [kernel, stdlib]}, {mod, {sample_app, []}} ]}.

The @PACKAGE@ and @VERSION@ parts are substituted with the information supplied in the AC_INIT macro call in

Likewise, a file could be:

{release, {"@PACKAGE@", "@VERSION@"}, {erts, "5.6.1"}, [{kernel, "@ERLANG_LIB_VER_kernel@"}, {stdlib, "@ERLANG_LIB_VER_stdlib@"}, {@PACKAGE@, "@VERSION@"}]}.

The variables ERLANG_LIB_VER_kernel and ERLANG_LIB_VER_stdlib contain the version numbers of the installed libraries named kernel and stdlib. To define such variables automatically with the versions of the libraries actually installed in your system, you just have to call the standard AC_ERLANG_CHECK_LIB Autoconf macro in your file, e.g.:


Note also that the ERTS version is not yet automatically determined by the standard Autoconf macros. However, Ruslan also proposed a new macro, AC_ERLANG_SUBST_ERTS_VER, to do that:

# AC_ERLANG_SUBST_ERTS_VER # ------------------------------------------------------------------- AC_DEFUN([AC_ERLANG_SUBST_ERTS_VER], [AC_REQUIRE([AC_ERLANG_NEED_ERLC])[]dnl AC_REQUIRE([AC_ERLANG_NEED_ERL])[]dnl AC_CACHE_CHECK([for Erlang/OTP ERTS version], [erlang_cv_erts_ver], [AC_LANG_PUSH(Erlang)[]dnl AC_RUN_IFELSE( [AC_LANG_PROGRAM([], [dnl Version = erlang:system_info(version), file:write_file("conftest.out", Version), halt(0)])], [erlang_cv_erts_ver=`cat conftest.out`], [AC_MSG_FAILURE([test Erlang program execution failed])]) AC_LANG_POP(Erlang)[]dnl ]) AC_SUBST([ERLANG_ERTS_VER], [$erlang_cv_erts_ver]) ])# AC_ERLANG_SUBST_ERTS_VER

You only have to put the code of that macro for instance in a acinclude.m4 file, placed in the same directory as the file, and to call it in


That way, the ERLANG_ERTS_VER variable gets automatically defined with the detected installed ERTS version, and can be substituted in your file, e.g. in {release, {"@PACKAGE@", "@VERSION@"}, {erts, "@ERLANG_ERTS_VER@"}, [{kernel, "@ERLANG_LIB_VER_kernel@"}, {stdlib, "@ERLANG_LIB_VER_stdlib@"}, {@PACKAGE@, "@VERSION@"}]}.

Note to myself: I should really really take a little time to submit the definition of Ruslan's AC_ERLANG_SUBST_ERTS_VER macro to the GNU Autotools team for inclusion into the standard Autoconf...


Nice write up

Couldn't have put it better myself.


Hi! This is bjlee, and we've met at the APNOMS 2007. remember?

I remember that we've talked about Erlang for a minute at the dinner table.
Because of that, I started to have interest in Erlang, and
started to use it as one of my programming Language.
In korea, the book "Programming Erlang" was released the other day,
and I have participated in translating the book in Korean as a reviewer.

Maybe someday, I hope to have a change to talk to you about Erlang
in the near future. :-P



I am the first one to comment ;)
I was using the jungerl/builder to create these files and now I can use autoconf.

Thank you,