MRvcmt (for Developers)

Checkout

  1. In your SLAC Public directory, create a work subdirectory (e.g., myCode).

Refer as necessary to: SLAC's Public Installation.

  1. At the command prompt, enter: MRvcmt
  1. From the MRvcmt Options menu, select: Cmt options
  1. First, set Paths as shown below:

Also see Alternative methods of setting
up Paths.

When setting up multiple
CMT Paths:

  • The 1st path should point to ".../myCode" directory.
  • The last (in this case, the 2nd) path should point to the "Base" release in the ".../builds" directory (e.g., ".../GlastRelease-v9r9").

 

Caution! By convention, when CMT searches for a package, it uses the first occurence in its CMTPATH. Be sure to sequence multiple paths accordingly, so that when you perform a "make" operation, your edited file(s) are the one(s) used in the build.
 
Then set the CMT "root", "version", and "CMTCONFIG" fields to point to the CMT library required in support of the release build
you have chosen.

Set the fields at left to point to the cmt.exe in the version of CMT required by the "Base" release and consistent with the compiler you are using.

Check the "CMT status" box. The full path to your CMT executable should be
displayed in green. If it is not, recheck your selections and entries.

  Note: CMT versions rarely change; hence, you will normally not have to change these fields very often.
Alternative methods of setting up the Paths include:  
 

 
 
  • "from CMTPATH file" - Create a CMTPATH file and then browse to it; the path would look similar to:

$CMTPATH=$HOME/myCode:/nfs/farm/g/glast/u30/builds
/rh9_gcc32opt/GlastRelease/GlastRelease-v9r9

 
  • "from environment" - Select "from environment" and enter the environment variable from the command prompt. The command would look similar to:

setenv CMTPATH $HOME/mycode: /nfs/farm/g/glast/u30/builds/rh9_gcc32opt/GlastRelease/GlastRelease-v9r9

Note: The lines above are wrapped.

Tip: In practice, you might elect to install the release build and the external libraries on a local network or workstation, and your work area on your laptop.

In fact, you can use any combination of these assets as long as the files you wish to access are all available to your network, and the CMT options are set up accordingly.

With the 1st and 2nd paths set up as shown in step 4, above, the Packages Tree should look similar to:

  1. In the Packages Tree, click on your work directory (e.g., myCode) to select it, then click on Packages and select Checkout from the drop down menu.

 

The Checkout GUI will be displayed:

  1. Enter the name of the package you wish to checkout (e.g., AcdDigi), then click on .

    A list of valid tags in the CVS repository will be built.

  1. Enter the "Tag" (e.g. v1r17) of the package you want to check out.
  1. Select the path to the directory you wish the package to be checked out to (e.g., "...myCode").

If you wish to do a Recursive checkout, select it now and then click on the OK button.

Your Packages Tree should now look similar to:

Tip: In order to avoid confusion at CVS "commit" time, it is considered good practice to always increment the version number of the file you plan to edit (e.g., to v1r18) when you check them out.

If you are going to edit the file(s) in your work area, now is a good time to increment the version number(s) from the command prompt. Note: You may have to quit MRvcmt in order to access the command prompt. Or, you can input the command in the "User Command" field:

Other CVS Functions

As shown in the "Cvs" drop down menu, you can perform many CVS functions from within MRvcmt, including "Commit"ting a file that you have updated, simulating "-n" an update to a file that you have already checked out and edited but, in the meantime, someone else has modified, "Update" your file, etc.

Also See:

 


 

Last updated by: Chuck Patterson 08/10/2006