Difference: LHCbSoftwareTrainingBasics (91 vs. 92)

Revision 922013-07-09 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbSoftwareTutorials"
<!-- Note to editors of this page: The following TWiki Variables are defined for this page: GAUDIVERSION and DAVINCIVERSION -->
<!-- They correspond to the last version for which these instructions have been verified, and should be consistent with each other -->
<!-- To change their value, exit edit and go to "More topic actions" -> "Edit settings" -->
Line: 168 to 168
  For a package with name myPackage, CMT itself defines an environment variable MYPACKAGEROOT that contains the package location.
Changed:
<
<
The full set of commands that can be used in a requirements file is described in the CMT manual. Some of the most useful commands are shown below.
>
>
The full set of commands that can be used in a requirements file is described in the CMT manual. Some of the most useful commands are shown below.
 |
# Lines beginning with the symbol '#' are treated as comments. 
# Blank lines are ignored. 

Line: 230 to 230
  Most CMT commands, but not all, operate on requirements files, and must be given from a package's cmt directory. If a requirements file includes lines indicating that other packages are used, then these packages will be searched for in locations specified by the project environment, and the requirements files of each used package is processed in turn.
Changed:
<
<
The CMT manual should be consulted for the full set of CMT commands, but a useful subset is given below.
>
>
The CMT manual should be consulted for the full set of CMT commands, but a useful subset is given below.
 
  • Perform package configuration - that is, create setup files and Make files:
cmt config
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback