Visual CMT for Linux

Updates (02/09/2004): VCMT4Linux is no more supported. There is a new multiplatform (Windows and Linux) GUI, called MRvcmt (Multiplatform Ruby Visual CMT). You can find information at the following link:

http://www.fisica.uniud.it/~glast/MRvcmt/

or contact the following persons:

Marco Frailis
Riccardo Giannitrapani

I have developed a Visual CMT for Linux platform using the ruby scripting language and FXRuby (an extension of ruby which add the FOX gui ). All features are taken from Visual CMT for Windows and glastpack. The last head version in the GLAST cvs supports CMT version v1r14 except for the new "release" feature. To simplify installation I give the binaries of ruby and FXRuby in one only archive. Here it is the link:

rubyInst181.zip (contains ruby version 1.8.1, FXRuby version 1.0.25 and FOX version 1.0.45)

If you use the above archive, please add to your environment the variable RUBY_HOME, which has to be equal to the directory in which 'ruby' dir is located. For instance, I have ruby in the following directory:

/scratch/users/frailis/Extlib/ruby

So, in my init file I specify:

setenv RUBY_HOME /scratch/users/frailis/Extlib

The PATH variable has to be updated with the path of the ruby binary:

setenv PATH $RUBY_HOME/ruby/bin:$PATH

(if you use the bash shell, use the export command instead of setenv)

If you have already Ruby and FXRuby installed in your system, you don't have to set neather RUBY_HOME nor to update PATH. In the previous version of VCMT I asked to set also the VCMT_HOME variable, but now is no more needed.

Finally here it is the Visual CMT package:

vcmtv0r3head.zip

This package is a copy of the actual head version of the vcmt4linux cvs package kept into the Glast Lat software repository. Please, if you want to keep updated, download the cvs head version.

VCMT needs the following applications to be already and properly installed in your system: CMT, xterm (not installed by default in the latest distributions), ssh.

Another thing that you should do is to remove the CMTPATH variable from your environment. If you use glastpack, starting vcmt, the program will automatically logout glastpack (it unlinks the .cmtrc file in your home).

Now simply write :

> ruby vcmt.rb

The first thing you have to do is to click on Options->CMT and set the working dirs (those in which Glast packages should be put), the root dir of the CMT installation, the current version of cmt and the value for the CMTCONFIG environment variable. For instance, my settings are:

cmt options

To insert a working dir, double click on the first empty element of the paths list: a text field will appear to insert a new path together with a button (with ellipses) that let you browse the directories and choose the one you want to add. To change a path, duble click on it. To remove one or more paths from the list, you can select multiple items (keeping the shift or control key pressed) and remove them pressing the Del key. The CMTCONFIG value set the directory in which binary files will be put. Due to GlastPolicy, the value set above (rh9_gcc32) influences also the search paths for external libraries.

If you check the "form CMTPATH file" checkbox, than you can use (read and modify) a CMTPATH file created by glastpack (there is one such file in each working directory created with glastpack). Visual CMT will create also a symbolic link (named .cmtrc) in your home, pointing to the selected CMTPATH file (behaving in the same way as glastpack); this way, glastpack and Visual CMT can be used simultaneously. To modify the paths in the CMTPATH file, simply change the paths into the path list and confirm the changes with the "apply" or "OK" button.

It's also possible to set, as debugger, emacs+gdb (thanks to Alex for his help) or DDD, using the options in Options->general.

The output tab in VCMT highlights compilation errors (in red) or warnings (in yellow).

Compilation errors highlightning

It's also possible to directly open into an emacs buffer the source containing an error or a warning (positioning the cursor at the right line). To activate this feature proceeds as follows:

edit your ".emacs" file in your home, adding the following line
(server-start)
start an emacs instance
when you double click in the vcmt output window on a line containing an error or a warning, an emacs buffer is automatically opened at the right place
if emacs, at a certain point, doesn't open any buffer (because you have opened and closed another emacs instance), restart the emacs server by pressing in emacs the keys 'Alt-x' and inserting the command 'server-start' followed by a return.

Tips

In the output window, right clicking with the mouse, you get a menu that let you remove the selected text in the window
the spawn button opens a shell on the cmt (or mgr) dir of the selected package and does automatically a source setup.csh letting the user execute the binary executables in the directory containing binaries
To do a recursive checkout of a package, use the checkout button to get a particular checkout package and set the recursive check box. Otherwise, checkout the package not recursively and than select it in the list of packages and press the add button. All remaining packages will be downloaded.

To do

KDevelop v3 integration
Show also packages inside a container in the list of packages
Some documentation about the Visual CMT functionalities
Automatic generation of the doxygen documentation (yet disabled)

ChangeLog

See the cvs ChangeLog file:

vcmt4linux cvs page

LINKS

Ruby Home

FOX Toolkit Home

FXRuby Home