To run, use the same procedure as for MRvcmt: just check out of cvs. Check out the HEAD for now. It's ready to be tagged; just hasn't been yet. On Linux you will also need to do
chmod +x MRStudio
to make it executable. Type MRStudio
with no arguments
to get help. To bring up the gui, type MRStudio gui
.
You must have ruby, but you only need the FOX library if you run the gui.
It is not necessary for command-line running, which is the default.
The first time you start up the gui FOX will be downloaded for you as was the
case for MRvcmt.
(Toby) Can you invoke it with a cmtpath file? (Riccardo) Not exactly. You can pass it a more comprehensive file which includes settings for cmtpath, CVS root, etc. If you don't pass it such a file, MRStudio will use the automatically saved settings, as MRvcmt does. Riccardo plans to add the ability to just specify a cmtpath.
Finally we need to deal with the long-term issue of how to keep our stuff and FSW in sync. (Richard) had a talk with Jana and they agreed (subject to JJ's approval; he's out of town this week) that what is needed is a way to trigger our builds using new FSW releases so that problems can be addressed as they appear. Porting the FSW build system to Windows would be ideal, but FSW has already made strenuous — and ultimately unsuccessful — efforts to do this.
previous | minutes index | next |