Opened 18 years ago
Closed 17 years ago
#28 closed Feature request (fixed)
Extent cmt/project.cmt file syntax/grammar
Reported by: | Owned by: | arnault | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | a. Usage | Version: | |
Severity: | normal | Keywords: | |
Cc: | OS: | All | |
If Other, could you precise: | Experiment: | Atlas | |
If Other, could you precise: | |||
Stack trace: | |||
Steps to reproduce: |
Description (last modified by )
The particular motivation for this came from LCGCMT, where LHCb wish to install it at CERN within an InstallArea, whereas ATLAS does. Currently this implies two separate installations, but the ability to do something like:
macro use_strategy "LHCb" without_installarea "ATLAS" with_installarea build_strategy $(use_strategy) private ...
or
project GEANT4 build_strategy with_installarea setup_strategy root private use GAUDI GAUDI_v16r3 Dans ce projet GAUDI n'est utilisé que pour obtenir la version de CLHEP et les flags de compilation
Change History (3)
comment:1 Changed 18 years ago by
Summary: | Extent cmt/project.cmt file → Extent cmt/project.cmt file syntax/grammar |
---|
comment:2 Changed 18 years ago by
Description: | modified (diff) |
---|---|
Experiment: | → Atlas |
OS: | → All |
comment:3 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
This is actually implemented and should be available for the v1r20 version.
An example of project file could be: