TMine External To-do and Status

Regularizing TMine

Now that the TMine external can be used with GlastRelease it would be good to keep the source somewhere in CVS more reputable than under users/jrb and to automate building and installation as much as possible. I propose the following:

New home in CVS

1. Make a new top-levl module, TMine-scons or TMineExt-scons, in CVS
2. Do a recursive copy of most of the contents of users/jrb/TMineDiv to the new module.  This should preserve history.
3. Make sym links for contents of SConsFiles (e.g. allExternals.scons, SConstruct, etc.) as is done for other containers

Possible gotchas

• Doing file copies and the like directly in the CVS repository makes me a little queasy.  Among other things, should check that resulting files and directories have the correct file permissions.
• Versions of SConstruct, allExternals.scons, etc. used by TMine may have diverged somewhat from the official set in SConsFiles. May need to incorporate some elements from the former into the latter.

If we want to SCons to automatically build new tags it would be only a small amount of additional work. We would then have immediate feedback if the new tag failed to build properly for some OS. However note that the builds created by the SCons RM are not organized exactly as required for externals, and that there is additional hand work (new tag of IExternal/TMineExt for CMT; modifications to allExternal.scons) before a new tag of an external can actually be used by anything.

Automation

• Create two python scripts, one to check out and build a tag, another to install in a suitable location. 

I've written .bat files to do these things for Windows (7.1 compiler only) with arguments like this:

   <span style="color: #008000"><strong>buildTMine</strong></span>  maj min patch [debug-opt]

   <span style="color: #008000"><strong>installTMine</strong></span> maj min patch [debug-opt] [destroot] [srcroot]

The first three arguments are required and specify major, minor and patch number for the cvs tag of TMine to be checked out.  debug-opt defaults to opt. buildTMine checks out and builds in a subdirectory of current working directory named after the cvs tag checked out. By default installTMine will look for the build to install in the same directory buildTMine would have created, and by default installs under the directory specified by the GLAST_EXT environment variable (not directly under, but where you would expect given external name, version, etc.).

Old Stuff

This table was created Jan.27 and updated March 1.