MIPP and SRT
We've decided to use FNAL's Software Release Tools (SRT) to manage
releases, packages, and the build system. SRT is used by several
experiments (CDF, D0, BaBar, MINOS).
SoftRelTools support at FNL is now the responsibility of
Bruce Greenway.
Installation and importing an offline release
Installation Guide
Getting Started
Work needed here to get MIPP software is a state where this is relevant...
(some user BABAR experience)
Documentation
The complete SRT manual is here.
SRT is a system to help manage independent development of software
packages. It works on top of cvs, although some cvs commands are still
needed. Developers as each site work from a common set of base
releases. These base releases can either be tagged (eg. release
'R01.02.03') or simply the most current (ie. "development"). The base
release contains a complete set of the software (include files,
libraries, executables) which developers can compile and link
against. Software development is done in "test releases". Each
developer has their own test release that they work in. A test release
need only contain a small subset of the packages that a developer is
working on. The test release references the base release for the
missing packages.
SRT also simplifies the writing of GNUMakefiles and coordinates the
build process.
The basic srt commands you'll need are:
| newrel -t base dir |
      |
Create a test release in directory dir using the release
base as the base release.
|
| srt_setup -a |
      |
Setup SRT to use the current directory as the test release.
|
| addpkg -h package |
      |
CVS checkout the module package and add it to the current
test release
The -h flag say to grab the "head" version (most up-to-date) of
the package from the cvs repository.
|
Trouble shooting
Not much experience to report.
Questions, comments to:
messier@huhepl.harvard.edu
Back to main MIPP offline software page