''(Grigory)'' == tdaq-common == The AtlasCore Offline project depends on the tdaq-common TDAQ project. The latter can be found, e.g., on AFS {{{/afs/cern.ch/atlas/project/tdaq/cmt/tdaq-common/}}} An example setup for the x86_64-slc6-gcc46-opt platform build on an SL6 machine can be: {{{ $ . /afs/cern.ch/sw/contrib/CMT/v1r25/mgr/setup.sh $ export CMTCONFIG=x86_64-slc6-gcc46-opt $ export CMTSITE=CERN $ . /afs/cern.ch/sw/lcg/contrib/gcc/4.6.2/x86_64-slc6-gcc46-opt/setup.sh }}} Then, assuming that the source code is available in the current directory: {{{ $ cd tdaq-common/tdaq-common-01-20-04/TDAQCRelease/cmt $ { \time cmt br "make VERBOSE=1 && make inst VERBOSE=1"; } >& cmt-br-make-make-inst.log& $ { \time cmt br -make -j1 -k check VERBOSE=1; } >& cmt-br-make-j1-k-check.log& }}} Another Make target is rpm. ''(Christian)'' I have installed tdaq-common into /exp/si/cmtng/tdaq/tdaq-common/tdaq-common-01-20-04 I have created a setup script /exp/si/cmtng/tdaq/setup.csh which contains: {{{ source /afs/cern.ch/sw/contrib/CMT/v1r25/mgr/setup.csh setenv CMTCONFIG x86_64-slc6-gcc46-opt setenv CMTSITE CERN source /afs/cern.ch/sw/lcg/contrib/gcc/4.6.2/x86_64-slc6-gcc46-opt/setup.csh }}} My session: {{{ cd /exp/si/cmtng/tdaq/tdaq-common/tdaq-common-01-20-04/TDAQCRelease/cmt setenv CMTPATH /exp/si/cmtng/tdaq/tdaq-common/tdaq-common-01-20-04 cmt config cmt show uses cmt br cmt show uses cmt br "make VERBOSE=1" > & cmt-br-make-make.log }}} Somme immediate comments on requirements of tdaq (made with Antoine & Sébastien) Indeed packages are either: 1. simple packages with mainly libraries & applications 1. of non standard Policy packages === Comments: === * Simple packages should be converted into Yaml easily * Policy packages require manual construction of hwaf "functions" * Remains the question of "tags" * what is the replacement concept? ("variant"?) * there are "automatic" variants (deduced from the platform/hardware/... introspection) - how to express them * and non automatic variants (eg with or without graphic) * how to implement in hwaf * how to express in yaml (or more generally in declarative language) * how to express the different forms of macro/set values? * Questions: * how to express the Yaml form of path/path_append/path_prepend/path_remove === Conversion from requirements to xml === {{{ cd /exp/si/cmtng/tdaq/tdaq-common/tdaq-common-01-20-04/ python parse.py }}}