BuildingTheNeoFramework

A tiny portion of the tools provided with babel are handy to build and run Ccaffeine with Neo-based components. Specifically, we use babel-libtool and babel-config for handling portability issues. The babel runtime environment and the babel compiler are NOT required. If you have another libtool installation compatible with libtool 1.5.10, you may be able to use it instead of babel-libtool. Beware, many libtools are not 1.5.10 compatible.

The first step is to obtain, build, and install babel, but you can disable most of the features. Ben recommends running babel's configure with at least:
--disable-fortran90 --disable-f77 --disable-java --disable-python --without-sidlx
Consistency of build options for C++ codes is critical as well. If you plan to use MPI and an mpi compiler wrapper anywhere in your code, you should include that information when building babel by setting the environment variables CC and CXX to point to your compiler wrappers before configuring babel. Example:
CXX=mpiCC
CC=mpicc
Once babel is configured, you can remove these variables from your environment and Ccaffeine and cca-spec-neo will pick the compiler correctly from babel.

When configuring cca-spec-neo, use the option
--with-babel-libtool=/full/path/of/bin/babel-libtool
to tell us where you installed babel-libtool. If you are using some other libtool, just give that tool's path. We don't require that the name of the program be exactly babel-libtool.