Ccaffeine "lemur" Source and Build

The final feature set is in to Ccaffeine for SC03. If you want to check it out get the version tagged "lemur":

cvs -d  $USER@cca-forum.org:/cvs/ccaffeine/repository co -r lemur ccafe

The tar ball for Ccaffeine as of October 19, 2003 is located here. This includes Ccaffeine and the two specification directories: "cca-spec-babel" and "cca-spec-classic" (if you are only using "classic" you don't need the babel specification but you will get it anyway). This does not include Babel which is available from here. Only Babel 0.8.6 or 0.8.7 are recommended.

• Python is now a configure parameter (--with-babel-python) and builds all of the python bindings to Ccaffeine in Babel. There is a special test (in ./ccafe/bin/test-python-bs) that checks the python bindings too.
• By binding the Port property "GoPort_Spawns_Thread" to "true", Ccaffeine will spawn a thread around that particular GoPort. The other GoPorts will behave as they always have. There is also a test for this one in ./ccafe/bin/test-GoThread. See ./ccafe/cxx/dc/component/GoThreadComponent.cxx for an example component.
• The xml .cca files that were largely defined by Boyana are now fully implemented and also end with the ".cca" extension. The old style .cca files will work as they did before.
• The "Goodbye Kiss" paradigm (ComponentRelease interface) is implemented for the Babel side of Ccaffeine but the classic side will remain the same. Neoclassic will implement something similar when it gets off the ground.

So here is the log file from the build if you are anxious to see it now. A few words may be in order to explain it, though.

This was built on my laptop using a uid I use only for this kind of testing. This helps, but is still no guarantee that Rob or Ben-specific stuff didn't creep into the build. Also, you will note that I did not use a prefix so all of the code is installed in the build direcories, but remember that even so, the make install directive is not optional, and little will work without it. This also uses the normal mpich from Argonne and without the mpd daemon. In this case you must use ssh or rsh configured properly for MPI to work.