This repository contains the installation routines of all the external software needed to compile and use FairRoot. To simplify the installation procedure of all these packages we provide a set of scripts which will automatically download, unpack, configure, build‚ and install all required software.
The script needs a complete build environment to compile all the source code. A list of all needed system packages can be found in the DEPENDENCIES file. All these system packages are installed using the package manager of the used Linux flavor. A list of complete command lines to install all packages in one go are also added in the DEPENDENCIES file, so one only has to cut-n-paste the appropriate command line to a terminal window and start the installation.
This Release was tested on following systems:
| System | Version | Compiler |
|---|---|---|
| Cent OS | 7 | gcc 6.2.0 |
| Debian | Jessie | gcc 4.9.2 |
| Fedora | 27 | gcc 7.3.1 |
| OpenSuse | 42.2 | gcc 4.8.5 |
| OpenSuse | 42.3 | gcc 4.8.5 |
| OpenSuse | Tumbleweed (220518) | gcc 7.3.1 |
| Ubuntu | 16.04 | gcc 5.4 |
| Ubuntu | 18.04 | gcc 7.3.0 |
| Ubuntu | 18.04 | gcc 8.0.1 |
| macOS | El Capitan (10.11.6) | Clang 8.0.0 |
| macOS | Sierra (10.12.6) | Clang 9.0.0 |
| macOS | High Sierra (10.13) | Clang 9.1.0 |
To start the installation procedure one has to run the configure.sh script which is found in the main directory of FairSoft from within this directory. If the script is called without parameters one is guided through some menus to choose the appropriate setup.
FairSoft> ./configure.sh
In the first menu one has to define the compiler which should be used for the installation. The normal choices would be gcc for Linux and Clang for Mac OSX. The compiler must be installed on the system. If one choose a compiler which is not installed, the installation procedure will stop when checking for the prerequisites defined above.
In the second menu one has to decide if the packages should be installed in debug, normal or optimization mode. If one choose the optimization mode one should also define the correct optimization flags in the file scripts/check_system.sh, even if there are some default settings. If unsure don't use the optimization option.
In the third menu you can choose to install FairMQ only components, if you choose Yes then you just need to specify the installation directory. This installation will skip all the simulation stuff and ROOT 6 installation.
In the fourth menu one has to define if one needs to install all packages to run a simulation. If unsure choose Yes.
If the previous choice was Yes one has to define in the next menu how to handle the Geant4 data files. These files have after installation a size of approximately 650 MB. If you don't intent to use Geant4 you should choose Don't install, if unsure choose one of the other options described below.
If the data files should be installed it is normally save to choose the option Internet which will download the files and does the installation automatically when installing Geant4. Only if your system cannot download the files during installation, choose the Directory option. In this case one has to put the files into the transport directory so that they can be installed. One can download the files from the following webpage.
http://geant4.cern.ch/support/download.shtml
In the next menu one has to decide if the python bindings for Geant4 and Root should be installed. The python bindings are only needed for the Ship experiment, so if unsure choose No.
In the last menu one has to define the installation directory. All the programs will be installed into this directory. One shouldn't use as installation directory a directory which is used by the system (e.g. /usr or /usr/local). Since it is possible to install several version of "FairSoft" in parallel it is advisable to use a name tag in the directory name (e.g. <install_dir>/fairsoft_mar15)
After passing all menus the installation process will check if all needed system packages are installed. If one or more packages are missing the installation process will stop with a detailed error message. In this case please install the missing system packages and start the installation again.
The installation procedure may take a long time depending on your computer. If the installation procedure stops with an error it is safe to start the script again. It will check which packages have been already compiled and installed successfully and will skip these packages.
As an alternative for experienced users it is also possible to pass an input file to the script which defines all the needed information. The configure.sh script will check if all variables are defined in the input file and if the values are allowed. In case an error is found the script will stop with an error message. Three example files (automatic.conf, grid.conf, and recoonly.conf) can be found in the main directory of FairSoft.
| Package | Version |
|---|---|
| cmake | 3.11.1 |
| gtest | 1.7.0 |
| gsl | 1.16 |
| icu4c | 53.1 |
| boost | 1_67_0 |
| Pythia6 | 416 |
| HepMC | 2.06.09 |
| Pythia8 | 212 |
| Mesa | 7.10.3 |
| Geant4 | 10.04.p01 |
| xrootd | 4.8.3 |
| ROOT | 6.12.06 |
| Geant321+_vmc | v2-5 |
| VGM | v4-4 |
| G4VMC | v3-6 |
| MillePede | V04-03-04 |
| ZeroMQ | 4.2.5 |
| Protocoll Buffers | 3.4.0 |
| nanomsg | 1.0.0 |
| FlatBuffers | 1.9.0 |
| MessagePack | 2.1.5 |
| DDS | 2.0 |
| FairMQ | 1.2.3 |
| FairLogger | 1.2.0 |
In case the python bindings are build the following additional packages will be installed
- XercesC 3.1.2
- G4Py Version which comes with Geant4
The installation script is mainly meant for one time installation of all packages. For developers we provide also another script which can remove the temporary files produced during compilation and the installed files for each of the packages. The script takes care also to delete all other packages which depend on the package which is removed. As an example given if you remove root then also geant4, vgm and geant4_vmc will be removed since these packages depend on root.
The script is either called with one parameter which is the package name
./make_clean.sh root
to remove only the temporary files or with the second parameter all
./make_clean.sh root all
which will also remove the files installed into the installation directory.