Next: Questions
Up: l1soft_0906_sworg
Previous: Directory Structure (3)
Overview
- Becoming an ATLAS standard (slowly)
- CMT is single C++ program which uses a requirements
file in the src/cmt directory of each package
to build and run a Makefile.
- The Makefile is constructed from a number of fragments
supplied with the CMT package.
- CMT interworks with CVS (but doesnt require it).
Features
- The requirements file can specify the desired outputs:
binary applications, libraries or other documents.
- You can set global options for the package and for each
output.
- Packages can "use" other packages. In this way they
also inherit all their options (but can override them).
Global options for all packages can be set this way.
- All packages get version numbers. You can build a distribution
by useing the latest versions of all packages (eg in
a separate build package) and doing cmt broadcast make.
Comments
- CMT has a preferred directory structure which is not the ATLAS
one, but it can be customised to be so.
- Currently missing equivalent to make install
- Support for generation of code (eg by moc) would need to be
added as a new document or language type.
- Feedback from ATLAS evaluations seems (weakly?) favourable.
Next: Questions
Up: l1soft_0906_sworg
Previous: Directory Structure (3)
Murrough Landon (m.p.j.landon@qmul.ac.uk)