Getting and Installing CMT

Obtaining the code

CMT is supported by Christian Arnault at LAL. For GLAST developers, a version of CMT has been checked into the central GLAST CVS repository. See below for the version that all GLAST developers should use.

  mkdir CMT
  cd CMT
  cvs co -d version -r version  CMT 
  

This will install all of the CMT sources into an appropriate directory structure. It is possible to use a single installation of CMT to build multiple platforms (for example on an AFS or NFS mounted directory) and to share a single installation among users.

NOTE: currently unix users should be using version v1r8p1 of CMT, whereas NT users should be using v1r7 of CMT.

A new NOTE: (30-jan-2002) we have switched to v1r10p20011126 for both unix and windows.

28-Nov-2002: Now we use v1r12p20020606 which is available in the repository with that tag.

Building CMT

Windows:

• open the CMT/version/Visual/cmt.dsw workspace in Microsoft Visual C++
• select the cmt project as the active project, and (if you can, switch from Debug to Release)
• select Build... from the Build menu.

This will compile and link the CMT executable into the CMT/version/VisualC directory.

Alternately, if you have vcmt installed, just click the "build cmt" button after filling in the version number, and getting the code from CVS by clicking the checkout button in the "CMT setup" area.

unix:

• Move into the mgr directory of the CMT package. If you have checked CMT out from the repository as described above, you will need to issue the command

  cd v1r8p1/mgr

• Issue the following commands from the mgr subdirectory. Numbers preceding commands are for reference only and are not to be typed when issuing the commands.

  1) chmod +x *          [for some reason a bunch of scripts don't get checked out as executable]
  2) setenv CMTCONFIG `sh cmt_system.sh`
  3) ./INSTALL
  4) source setup.csh
  5) gmake
  6) ./INSTALL
  

  NOTES:
  • 1) and 2) are only necessary if the execute bit is not already set on these files, but there is no harm in executing the commands even if the bits are already set.
  • 3) saves a name for your current platform (e.g., i386_linux22) in the environment variable CMTCONFIG.
  • 4) builds the setup.csh script. Do not omit the "./"
  • 5) sets up some necessary environment variables for running CMT.
  • 6) builds the CMT executable.
  • 7) Does the installation. Don't forget the "./"

R.Dubois
Last Modified (J. Bogart): 12/02/2002 11:40