Linux Installation (Developers): Install the Configuration Management Tool (CMT)

Notice: The GLAST code has not been released to the public and is for use by members of the LAT Collaboration only!
Note: If you are working on a SLAC Linux machine and want to use SLAC Public's CMT installation instead of downloading CMT, you can do so by setting up your .cshrc file. (See Modify Local Environment: SLAC Public Installation.) If you are working offsite, you should download the CMT to your local machine.

To obtain CMT using the Glast Software Installer:

  1. Install CMT using the Glast Software Installer:

Note: If you are a Linux user and prefer using a command line installer instead of a GUI, see Linux Command Line Installer.

GUI Installer:

  1. Click on Launch Installer Now!

When prompted, select: Open with javaws.

Tip: If the Installer fails to open, check that you have javaws (typically located in /usr/java/bin/java).

    1. Follow the GUI instructions and install CMT.

      2. If necessary, refer to: Glast Software Installer.

    Note: After completing the installation -- and assuming you unpacked
    CMT in the directory /glast/tools -- you should have the following
    subdirectory:

      /glast/tools/CMT/vXrYpZ

    where the values of X, Y, and Z will depend on the version of CMT (e.g., v1r16p20040701 as of November 2004).

  1. Add the directory containing cmt.exe to your PATH environment variable.

      2. Caution! When developing on Linux, if there are multiple paths in the CMTPATH, at run time the wrong version of a library can be picked up. Linux developers are encouraged to use one directory when building and running applications via CMT. If you desire to build against a pre-built release, it is suggested that you:

      • Copy the desired build into your development area.
      • Replace or override release packages as needed with new development versions.
      • Do cmt broadcast cmt config.
      • Then build the new packages.
    1. Identify the type of system and the GLAST-supported Compiler:

      Note: The following example assumes the current compiler is Red Hat 9
      with gcc 3.2 and is installed in the default location; modify as appropriate.

      setenv CMTCONFIG rh9_gcc32

    1. Point to the CMT Location of the CMT Installation on Your Machine:

      setenv CMTBASE /software/CMT

    2. Add the Version of CMT (typically a part of the directory path to your
      CMT installation)

      setenv CMTVERSION v1r16p20040701/Linux
      source ${CMTBASE}/${CMTVERSION}/mgr/setup.

  1. In the mgr directory, modify the setup.sh and setup.csh files (e.g., glast/tools/CMT/v1r16p20040701/mgr/setup.sh) so that the environment variable
    CMTROOT    , initialized in these files, gets set to the right value for your
    installation:
  1. Assuming the installation directory is /glast/tools, change the line near
    the top of setup.sh from:

    CMTROOT=/1a1/CMT/v1r16p20040701; export CMTROOT

    to:

    2. CMTROOT=/glast/tools/CMT/v1r16p20040701; export CMTROOT

  2. In setup.csh change:

    3. setenv CMTROOT /1a1/CMT/v1r16p20040701

to:

setenv CMTROOT=/glast/tools/CMT/v1r16p20040701

Test your CMT Installation:

  1. At the command prompt, enter: cmt

Verify that a list of possible cmt command options is displayed.

 

Last updated by: Chuck Patterson 11/28/2007

 

 

05/22/2008