Installing from the source kit

On Unix platforms

First download the source distribution kit.

This results in a directory structure like:

<some root>/CMT/v1r<nn>p<xxx>/...
    

Then, you have to perform the installation by running:

unix> cd <some root>/CMT/v1r<nn>p<xxx>/mgr
unix> ./INSTALL
unix> source setup.[c]sh

  or

dos> cd <some root>\CMT\v1r<nn>p<xxx>\mgr
dos> call INSTALL.bat
dos> call setup.bat

    

At this stage, you may either build CMT yourself, or fetch from the download page some of the prebuilt binaries (note that even if you select to get one of the prebuilt binaries, you always have to first download the source kit).

unix> source setup.[c]sh
unix> [g]make

  or

dos> call setup.bat
dos> nmake /f nmake

    

Then CMT is installed, and read to be used. Users have then to connect to CMT by doing:

unix-csh> source <some root>/CMT/v1r<nn>p<xxx>/mgr/setup.csh

  or

unix-sh> . <some root>/CMT/v1r<nn>p<xxx>/mgr/setup.sh

  or

dos> call <some root>\CMT\v1r<nn>p<xxx>\mgr\setup.bat
    

On Windows platforms

Some of the global configuration parameters for CMT may optionally be installed as Windows registry entries (although the environment variables style of definitions is fully supported). This can be done using the install.exe facility available from the download page or using the standard RegEdit facility :

• HKEY_LOCAL_MACHINE/Software/CMT/root will contain the root directory where CMT is installed (eg. "e:").
• HKEY_LOCAL_MACHINE/Software/CMT/version will contain the current version tag of CMT ("v1r16" for this version).
• HKEY_LOCAL_MACHINE/Software/CMT/path/ may optionally contain a set of text values corresponding to the different package global access paths (similar to the CMTPATH environment variable.
• HKEY_CURRENT_USER/Software/CMT/path/ may contain a set of text values corresponding to the different package private access paths (complementary to the latter).