Build System


The build system uses the GNU Autotools and libtool. All platform-/compiler-dependent parameters should go into the file that is processed by Autoconf. The configure script accepts a few non-standard arguments. The most interesting ones to non-developers are:

For the full set of options, use configure --help.


Each directory with source files has its own file that is processed by Automake. All local variables defined in these files are prefixed with RB_ for RAPP Build, to avoid accidental clashes with Automake variables.

When the RAPP library is built, several convenience libraries are built and merged to form the final library. The compute/vector directory is a bit special. It is built two times from the same sources, resulting in two different convenience libraries. The first time it is built with no extra flags, producing an implementation using the SWAR vector backend. The second time we define RAPP_USE_SIMD to build a version with the SIMD backend instead. At the top level of the Compute layer, all three implementations (generic, SWAR and SIMD) are combined into the Compute layer convenience library. The function selection mechanism guarantees, if used correctly, that a function is only implemented once.

The build system in the compute/tune and benchmark directories are a bit special. When the configure script is run, it will check for the presence of an up-to-date pre-tuned configuration file directory. If found, a symbolic link compute/tune/rapptune.h is created to this file. During build time, this symbolic link will be used for selecting the appropriate implementations. The file benchmarkplot-<host>-<backend>-<wordsize>.html in the benchmark/arch directory is handled analogously. The symbolic links are only removed on distclean. The -<wordsize> part, corresponding to the word size used by the platform, is empty for the default size for the platform.

If the pre-tuned rapptune-<host>-<backend>-<wordsize>.h is present but the set of tuned functions has changed since it was generated, the default build behaviour is to generate a new tuning. Alternatively, with an explicit --enable-tune-cache option, untuned fallback values will be used to fill in the missing tuning numbers, but compiler warnings will be emitted for each such untuned function when building RAPP. This is of course not recommended, but may be useful e.g. when cross-compiling and the target system is not available for tuning at the time RAPP is built.

Next section: Tuning System

Generated on 1 Jun 2016 for RAPP Compute by  doxygen 1.6.1