Package: ALICE HLT This package implements the ALICE High Level Trigger analysis framework. All contributions are under the terms of the GNU General Public License as published by the Free Software Foundation. Also see files AUTHORS and THANKS. This packages is maintained by Matthias.Richter@ift.uib.no Comments, bug reports, suggestions welcome! ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + TOC ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + 1. Overview + 2. Requirements + 3. Setting up a version retrieved from CVS + 4. Modifying a distributed package + 5. Installation + 6. Documentation + 7. Further information + 8. Reporting bugs/Asking for support + 9. Committing to the AliRoot CVS ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1. Overview =========== This package provides a compilation of shared libraries of the ALICE HLT project and is intended for stand-alone compilation, i.e. not as part of the AliRoot compilation. - \b BASE: The base library (libHLTbase.so) provides the common interface for HLT processing components, the binding into the ALICE offline project AliRoot and a pure C interface to the HLT on-line framework (Publisher/Subscriber framework) - \b SampleLib: The sample library contains examples for component implementation and a tutorial. - \b TPCLib: The HLT code for the TPC - \b TPCLib/OnlineDisplay: HLT visualization code for the TPC - \b PHOS: The HLT code for PHOS - \b TRD: The HLT code for TRD 2. Requirements =============== The package needs both ROOT and AliRoot. Both must be set up in the usual way (ROOTSYS, ALICE_ROOT, library locations evtl. specified in LD_LIBRARY_PATH, ...). Actually, the BASE and SampleLib modules are not dependend on AliRoot. The TPCLib does. To set up a version retrieved from CVS, autoconf 2.57, automake 1.6 ,and libtool 1.4 or higher versions are required. Thats the versions which come with the Scientific Linux CERN 3. The same applies if you want to change the Makefiles. If your GNU build tools are too old, ask the maintainers for a distributed package. 3. Setting up a version retrieved from CVS ========================================== Skip this section if you have started from the tar ball. A version checked out from CVS requires a few steps to set up the Makefiles. Go to the directory and run autoreconf -i -f Then continue with the package configuration described in the 'Installation' section. 4. Modifying a distributed package ================================== If you are going the modify a distributed package you might need to re-make the GNU build system by running autoreconf -f -i Please notify the authors about bug fixes/corrections/extensions you made if you consider them worth to be merged into the project. Then continue with the package configuration described in the 'Installation' section. 5. Installation =============== Package build relies on the GNU triplet configure, make and make install. In order to keep the development directory clean, it is recommended to use a separate build directory. \b NOTE: Autotools creates the Makefiles from templates. All \b changes have to be done to the \b Makefile.am templates. It is recommended to read the complete section before the build process. 5.1 For the impatiant user -------------------------- mkdir build cd build ../configure make make install 5.2 Installation directory -------------------------- The default install directory is set to the current directory ($PWD). To override the default directory use the option --prefix=