Building Ccaffeine

Ccaffiene uses normal GNU tools for configuration and building. The ccaffeine build tree can be downloaded from the central server at cca-forum.org . There are extensive examples of the build process available on the web .

There are a variety of usable configurations that will produce a functioning framework. You can get a list of these options by typing: configure --help. For the first time though there are some common packages that should be installed on your machine up front:

• gcc (2.95.3, 2.96, 3.x)

• Java (>jdk1.2)

• BLAS, LAPACK (any recent)

• BOOST headers

• Babel

• Ruby (any recent)

After untarring the Ccaffeine distribution . There will be three directories at top level:

• dccafe: the top level Ccaffeine directory.

• cca-spec-babel: the CCA specification in SIDL (Babel) and its attendent Makefiles

• cca-spec-classic: the old CCA specification on which many components still run.

In a perfect world all that need be done at this point is to go into each of these directories and type "configure;make", but this is not a perfect world and your environment is likely to be unique. Examples of successful builds on our platform are:

• Configure and make the CCA specification:

  
  (cd ./cca-spec-babel; configure --with-babel=/usr/local/babel --with-jdk12=/usr/local/java;make)
  

  Configure and make the classic CCA specification (this is currently a necessary part of the build, because Ccaffeine itself relies on it):

• 
  (cd ./cca-spec-classic;configure;make)
  

• Configure and make Ccaffeine itself:

  
  (cd ./dccafe; ./configure  --with-cca-babel=`pwd`/../cca-spec-babel \
  --with-cca-classic=`pwd`/../cca-spec-classic \ 
  --with-mpi=/usr/local/mpich --with-jdk12=/usr/local/java \
  --with-lapack=/home/rob/cca/dccafe/../LAPACK/liblapack.a \
  --with-blas=/home/rob/cca/dccafe/../LAPACK/libblas.a; make)
  

The Ccaffeine build will take 5-10 minutes. A entire listing of the build process for Rob Armstrong's laptop is available on the web. At the end of the build (in directory dccafe) a fairly complete test is run on Ccaffeine. Your indication that all has gone well appears at the very end of the (considerable) output that the Ccaffeine build process generates:

=====================================================================
Testing the Ccaffeine build ...
didn't crash or hang up early ...  looks like it is working.
done with Ccaffeine tests.
=====================================================================

This is your indication that all is in readiness and that Ccaffeine ready for a test drive. So it is time to go to the next section.