Building Fuego using GNU Autotools

Building from a distribution (released version)

./configure
make

Interesting options to configure are --enable-assert for enabling assertions or --enable-optimize=no for switching off optimizations. ./configure --help returns a full list of options.

Building a development version checked out from SVN

aclocal
autoheader
autoreconf -i

The above commands need to be run only initially. Then the compilation works as in the previous section.

After adding or removing files or doing other changes to configure.ac or a Makefile.am, you need to run autoreconf again before doing a make. A better way is to configure your makefiles with ./configure --enable-maintainer-mode. Then a make will automatically check, if configure.ac or a Makefile.am have changed and recreate the makefiles before the compilation if necessary.

Installing Fuego

sudo make install

Running tests

The following command compiles and runs the unit tests (and also runs other tests):

make check

Building debug and release version

Assuming that you want to build a debug and release version in different directories. This is called a VPATH-build. In this example, we choose fuego/build/autotools/debug and fuego/build/autotools/release as the build directories:

cd fuego
mkdir -p build/autotools/debug
cd build/autotools/debug
env CXXFLAGS=-g ../../../configure --enable-assert --enable-optimize=no

cd ../../../
mkdir -p build/autotools/release
cd build/autotools/release
../../../configure

Then the command make should be run in fuego/build/autotools/debug or fuego/build/autotools/release.

Further documentation links

• Autotools: a practitioner's guide to Autoconf, Automake and Libtool
• GNU Autoconf, Automake, and Libtool (some of the examples are not yet updated to newer versions of Autotools; still a useful reference)
• GNU Autotools manuals: Automake, Autoconf, Libtool

---

17 Jun 2010 Doxygen 1.4.7