Once the distribution kit is downloaded, and untarred, resulting in a directory structure like:
you have to perform the installation by running:<some root>/CMT/v1r12/...Then CMT is installed, and anybody may use CMT simply by doing:unix> cd <some root>/CMT/v1r12/mgr unix> ./INSTALL unix> source setup.[c]sh unix> [g]make or dos> cd <some root>\CMT\v1r12\mgr dos> call INSTALL.bat dos> call setup.bat dos> nmake /f nmakeunix-csh> source <some root>/CMT/v1r12/mgr/setup.csh or unix-sh> . <some root>/CMT/v1r12/mgr/setup.sh or dos> call <some root>\CMT\v1r12\mgr\setup.bat
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 ("v1r12" 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).