berabera べらべら blahblah

I have sent patches to GNU Autoconf to add new macros for testing Erlang modules, include files, and functions: AC_ERLANG_CHECK_MOD, AC_ERLANG_CHECK_HEADER, AC_ERLANG_CHECK_LIB_HEADER, and AC_ERLANG_CHECK_FUNC. I have also sent a patch to fix the AC_RUN_IFELSE macro which executes Erlang test code, so that this macro cleanly fails if the code doesn't compile, and another patch to fix the AC_COMPILE_IFELSE macro, which tests that Erlang test code compiles (this is a long known Autoconf bug).

GNU Autotest is GNU Autoconf's unit testing tool. and is very generic, portable and simple. Autotest is therefore well suited to run tests using other testing tools, such as EUnit (Erlang/OTP's unit testing tool), JUnit, etc. I just added to GNU Autoconf the AT_CHECK_EUNIT macro to run EUnit unit tests in Autotest testsuites. It is the first Autotest macro to integrate such an external testing tool, and will be included in the next version of GNU Autoconf (> 2.64). A complete, working example project using AT_CHECK_EUNIT can be downloaded in autotest-eunit-demo-1.0.tgz. This article shows how to use AT_CHECK_EUNIT by explaining the important parts of this example project.

I have restarted actively maintaining the Erlang support in GNU Autoconf. Autoconf version 2.64 has been released on July 26th, which contains a few changes to its Erlang support.

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! (^_^);