Installing the the CCA Tools
1. Download
cca-tools-installer-0.2.8.tar.gz and unpack it, e.g., with
tar xfz cca-tools-installer-0.2.8.tar.gz
Note: The installer used to be named cca-tools-contractor prior to 7/2010.
2. Create a subdirectory for each configuration you wish to build, for example, to build using only default options (see item
3 below for information on how to customize the build):
cd cca-tools-installer-0.2.8
mkdir default-build
cd default-build
../contract.py --configure
../contract.py
Upon the successful completion of the above commands, you should have a complete installation of the CCA tools in the
cca-tools-installer-0.2.8/default-build/install/ directory.
Note that the default Babel version is 1.4.0, which is not backward compatible with Babel 1.0.8, so by converting your projects to use 1.4.0, you will no longer be able to use Babel 1.0.8 with them. If you wish to build the CCA Tools with Babel 1.0.8, make sure to explicitly configure the build first, e.g., with "../contract.py --configure babel_version=1.0.8" before running "../contract.py".
3. You may also want to specify configuration options, such as a prefix, different compilers to use, an MPI prefix, etc. For more detailed information on the configuration options, refer to the
CCA Tools wiki page.
4. If you are using bocca to manage your project, note that after upgrading to a new version of the CCA Tools, you will need to do the following in the top-level directory of existing bocca projects:
bocca update --store
bocca config --update
./configure <your configure options>
The "bocca update --store/-s" command regenerates the internal project representation using the new version of bocca. Note that after doing this, you will no longer be able to switch to an old version of bocca. The "bocca config --update/-u" command updates project default settings and regenerates project-specific build files. You can see what configure options you used last time with the "head config.log" command. Make sure to use the path to the newly installed CCA tools in the --with-ccafe-config configure option.
Manually installing the CCA Tools
The complete and latest build of the Sumo can be downloaded
here. Individual packages that comprise the latest Sumo are available
here. Previous versions are available
elsewhere.
Description
The following packages can be built depending on the configuration (in this order):
- Chasm
- Babel
- CCA Specification Babel bindings (classic, neo, babel)
- Ccaffeine CCA framework
- Ccaffeine GUI
Supported Platforms
The CCA Tools distribution should work on most
Linux distributions, and theoretically
Mac OS X (requires GNU tools).
All of the tools work on
IBM AIX, but the CCA Tools distribution is not currently setup to build automatically for this platform without extra environment variable settings.
The CCA Tools have not been ported to Windows. They should work fairly easily on top of Cygwin or MinGW. A native Windows port would require a good deal more work. The core development team does not currently have funding to pursue a Windows port, but we would be happy to assist others.
If you're interested in a platform we don't currently support, please let us know!
We're establishing routine testing of the tools (build and regression) on as many different platforms as possible. The
Tools Testing Patforms page is tracking this effort.
HPC Systems and Static Frameworks
Many systems, like the
Cray XT and
IBM BlueGene?, do not support dynamically loadable component objects.
For instructions on how to build a "static" CCA framework for these systems, or for other rare purposes, please see
HOWTO: Static Ccaffeine Framework.
Development
The Subversion repository for the Contractor-based installer of the CCA Tools can be checked out with
svn co https://cca-forum.svn.sourceforge.net/svnroot/cca-forum/cca-tools-installer/trunk cca-tools-installer