Help for Visual CMT

Help for Visual CMT

This is a visual interface around CMT, designed to help manage multiple packages, including options to run cvs, Visual Studio, doxygen, and arbitrary commands.

_____________________________________________________________________________________________________________________________

Navigate this page

_____________________________________________________________________________________________________________________________

Packages

This is a list (or subset) of the packages currently known to CMT. If you modify the path it will be reloaded automatically.

One package at a time can be selected by clicking on the list. It is then used in the actions section.

Buttons below the list are:

refresh

Refresh the package list. Not normally needed.

filter

Filters the list to contain only the selected package and the ones it depends on.

checkout

Check out a package from the cvs repository. A dialog box will prompt for the following:

the name of the package, which must be in cvs
the cvs revision. Leave blank for a development version, or head of the MAIN branch
a directory path to store the package, one of the components of the CMT path.
a cmt version identifier to assign to the package. Leave blank for a standard checkout, to assign the cvs revision. If revision=version, the package will be checked our read-only.

add

Does a recursive checkout of all packages used by the selected package that are not in the package list.

delete

Remove the selected package

new

Create a new package. A dialog box will prompt for the name, version, and directory. Executes the cmt command "create".

spawn

"Spawns" a new DOS window in the root of the selected package, with the proper execution environment set up

_______________________________________________________________________________________________________________________________

Actions

All of the buttons and input fields below implement various actions on the current package. The broadcast mode toggles, local or global represent a "broadcast" mode, in which the action is first performed on all the dependent packages in the same folder (local) or all (global), then on the selected one.

When VCMT is processing an action, a the action being performed will be indicated, with the number of actions still to do. The abort button will be then enabled to allow one to abort the (future) actions.

Most actions are carried out in a separate command window, which is started minimized. It can be restored to view the progress, or killed if things are going wrong. When the action is finished, the results are copied to the package output window.

________________________________________________________________________________________________________________________________

msdev

The buttons in this section setup, or invoke, the Microsoft Developer Studio (msdev) application to perform various actions.

setup: Run the cmt "build msdev" command to create msdev project files in the directory Visual. Also creates a file mgr/setup.bat that will set all environment variables known to cmt. After this is done, the dropdown list project is filled with the names of the found .dsp files.
start: Runs mgr/setup.bat, then msdev itself in the package directory. (setup must have been done first.) Note that all environment variables will be set for the debug or release environment.
sysclean: Remove the directories Visual, Win32 and Win32Debug

The following buttons initiate a check for the existence of mgr/setup.bat, the Visual directory, and that mgr/setup.bat is newer than mgr/requirements. If any of these conditions fails, a setup is run. If no project is selected, "all" is assumed.

make: Make the selected project.
clean: Clean the selected project.
rebuild: Rebuild the selected project.

_________________________________________________________________________________________________________________________________

Run an application

If the selected msdev project is an executable, then the run button executes

mgr\setup.bat,
the executable.

Output goes into a separate DOS window while the application is running, and is captured into the appropriate action window when it finishes. At the moment, only one application can be run at a time.

The input box is for command-line parameters. Note that a <cr> will unfortunately not start the app, but a <tab><cr> will have that effect.

__________________________________________________________________________________________________________________________________

cvs actions

Perform the action in the package root directory. Assumes that the package is under cvs control, with an appropriate CVS subdirectory at the root. Note that cvs commands besides these can be issued as "dos" commands.

update: Does a "cvs update -d -P" where the -d means get new folders, -P prune empty ones.
-n update: Does a "cvs -n update -d -P", allowing to check what updates would occur. (Better to do before update.)
checkin: Does a "cvs checkin". A notepad window will open for comments if files need checking in. Can be; aborted by dismissing the window, and responding "a" in the dos window.
status: Does a "cvs status -v mgr/requirements". This allow you to see if the package was checked out with as; sticky tag, and what tags are available. An error will occur if the package is not under cvs control, perhaps created with a package new.
import: Import a newly created package into cvs, assigning the version as a vendor tag. User is shown the exact; command and prompted for permission. Note that the package then needs to be deleted and checked out to have a version under cvs control.
rtag: Tags the current package in the cvs repository with its version, which should be a development version.; The user is shown the exact command and prompted for permission.

___________________________________________________________________________________________________________________________________

dos actions

Run any "dos" command (e.g., dir) in the root of the selected package. You must then click the associated "run" button, or, after entering a command, simply hit the tab key, then enter. Very useful for editing a file (just enter "notepad mgr\requirements" for example.)

___________________________________________________________________________________________________________________________________

Doxygen

Create and/or display in a browser window the doxygen-ated content of the package. The folders <package-name> and src are searched recursively if found, with the output saved in doc/doxy-html. (Since this is generated, it should not be checked into cvs.) Images should be put into doc/images.

If a file Doxyfile is found the the doc folder, it will be appended to the standard file.

See the doxygen home page.

___________________________________________________________________________________________________________________________________

CMT setup

path: The CMTPATH is a list of file paths that CMT searches for packages. The radio buttons User and System; allow one to define elements in the Current User, and Local Machine registries, respectively. Enter paths a line at a time in the window below.
root: The path to the CMT package itself.
version: The folder under the root to define the actual CMT version to use.
site: Allows setting the CMTSITE variable, not used by GLAST.

Buttons are provided or initial checkout and build:

checkout: do a cvs checkout of the selected CMT version into the root directory.
build cmt: use msdev to (re) build the selected version of cmt.exe.
debugger: Executes a "debugger" statement, which will start the debugger if installed and enabled.

_____________________________________________________________________________________________________________________________________

Last modified on December 02, 2002

Back to setting up VCMT