Dashboard DartConfig

Sample DartConfiguration.tcl

This is the DartConfiguration.tcl file from one of our Linux machines that is doing a nightly build of the tagged Slicer release 2-4-patches. You would need to modify this file to point to the appropriate directories for your build. The script genlib.tcl builds all of the libraries (VTK, ITK, etc.) that Slicer is dependent on, so we use that as our configure step. You could also put your own configure script there instead. Our make command is a script called cmaker.tcl, which we pass the clean flag. You could put your own make command here (e.g. make, gmake). This build doesn't use purify or valgrind, and currently isn't doing any testing.

 # Configuration directories and files
 SourceDirectory: /home/hayes/dart-cvs-release-2-4-patches/slicer2
 BuildDirectory: /home/hayes/dart-cvs-release-2-4-patches/slicer2
 
 # CVS options
 # Default is "-d -P -A"
 # If you want to check out a tagged release, specify it in the options
 # as:   -r tagged-release-name
 CVSUpdateOptions: -d -A -P -r release-2-4-patches
 
 # Site is something like machine.domain, i.e. pragmatic.crd
 Site: glider-cvs-release-2-4-patches
 
 # Build name is osname-revision-compiler, i.e. Linux-2.4.2-2smp-c++
 BuildName: Linux-Redhat-9-g++
 
 # Submission information
 DropSite: www.na-mic.org
 DropLocation: /cgi-bin/HTTPUploadDartFile.cgi
 DropMethod: http
 TriggerSite: http://www.na-mic.org/cgi-bin/Submit-Slicer-TestingResults.pl
 
 # Dashboard start time
 NightlyStartTime: 1:00:00 EST
 
 # Commands for the build/test/submit cycle
 ConfigureCommand: /usr/bin/tclsh /home/hayes/dart-cvs-release-2-4-patches/slicer2/Scripts/genlib.tcl
 MakeCommand: /usr/bin/tclsh /home/hayes/dart-cvs-release-2-4-patches/slicer2/Scripts/cmaker.tcl --clean
 CVSCommand: /usr/bin/cvs
 
 # Testing options
 # TimeOut is the amount of time in seconds to wait for processes
 # to complete during testing.  After TimeOut seconds, the
 # process will be summaily terminated.
 # Currently set to 25 minutes
 TimeOut: 1500
 

If you are considering performing memory checking using Valgrind or Purify, or performing a coverage testing using gcov, you can optionally add the following:

MemoryCheckCommand: /usr/local/bin/valgrind
MemoryCheckCommandOptions: --weird-hacks=lax-ioctls -q --leak-check=yes --show-reachable=yes --num-callers=100 -v
MemoryCheckSuppressionFile: /home/hayes/dart-cvs-release-2-4-patches/slicer2/SlicerValgrindSuppressions.supp
CoverageCommand: /usr/bin/gcov