-
+
|
- |
+ |
|
|
The code is actively maintained on Linux and HP (both CC and aCC +compilers). It also runs on Compaq OSF1 and SunOS. We welcome feedback from +the installation on other systems and we will be happy to consider +modifications and corrections necessary to make the installation possible. + +
The disk space required for a full installation of AliRoot is 360MB for +the system itself and 120MB for the ROOT system. + +
The installation is performed via the + +gmake program. gmake is the +GNU version of make, it is free and, +if missing on your machine, it can be loaded from the GNU Internet site + +ftp://ftp.gnu.ai.mit.edu/pub/gnu/make. gmake is compatible +with the standard UNIX make and on the CERN ion WGS +make is aliased to gmake. The only files you need for +gmake are the executable gmake +and the script autoconf, therefore you can copy such files from +any site in a directory in your path. + +
ROOT is available for many platforms, therefore in most cases +no ROOT installation is required. To install ROOT on your machine, +connect to the web site and follow the +link downloads. Usually you should get the latest release, unless +announced differently by the news of the Off-line Project. + +
All you need to do is download the compressed tar file, that usually is +called root_v...tar.gzuncompress and untar it (we supposed you +downloaded the tar file in your $HOME): + +
+$ gunzip root_v...tar.gz
+
$ cd directory # name of the directory where you want ROOT to sit
+
$ tar xvf ~/root_v...tar
+
+
+
When tar ends, you will have the full root directory tree, with already +installed libraries for your platform. + +
The following shell variables should be defined in the login scripts: + +
| variable | value |
|---|---|
| ROOTSYS | directory/root + |
| LD_LIBRARY_PATH | +$LD_LIBRARY_PATH\:$ROOTSYS/lib |
| SHLIB_PATH | +$SHLIB_PATH\:$ROOTSYS/lib |
| PATH | +$PATH\:$ROOTSYS/bin |
At this point you should logout, login again and check that the symbols are set correctly. -
| File | Content |
|---|---|
| Either | |
| AliOfflineMM.mm-pp.tar.gz - | Code and the data files of ALICE Off-line |
| Or | |
| AliLibsMM.mm-pp.tar.gz - | Code and the data files of the auxiliary libraries |
| AliRootMM.mm-pp.tar.gz - | All the code and the data files of the AliRoot system |
MM.mm-pp is the number of the latest Major and -minor version and the patch number. Please refer to the -README file found in this directory for further information on file -content. The file(s) have to be unpacked into the $ALICE directory via the -command: - -
$ gtar xvfz Ali[...].tar.gz- - -
The tar file(s) can to be unpacked into the ALICE directory + via the command: + +
$ gtar xvfz V3.XX.tar.gz+ +
A script changeCVSRoot + is available to convert a CVS tree under user "cvs" to another + user. For example,
ChangeCVSRoot asmith+ +
$ cd $ALICE -$ cvsa co -d pro AliRoot +$ setenv CVSROOT :pserver:cvs@alisoft.cern.ch:/soft/cvsroot +$ cvs co -r Release-3-XX -d pro AliRoot ++ +
+$ cd $ALICE/pro +$ setenv CVSROOT :pserver:cvs@alisoft.cern.ch:/soft/cvsroot +$ cvs update -d
+
+$ rehash ++ +
This usually has to be done only once, after having defined the new PATH. +
@@ -135,13 +229,146 @@ root [1] .x menu.C
If the ALICE environment is set up correctly, the +$ALICE_ROOT/lib/tgt_$ALICE_TARGET directory is in the shared +libraries load path, and the $ALICE_ROOT/bin/tgt_$ALICE_TARGET +directory is in the PATH variable. This means that the command +aliroot will in fact correspond to the file +$ALICE_ROOT/bin/tgt_$ALICE_TARGET/aliroot. + +
This is convenient for the normal user, but as soon as the user wants to +modify one or more directories, this arrangement becomes inefficient +because if a local copy of one of the shared libraries is remade, the +linker will always find the official unmodified one that sits in the above +directory before the local one in the load library path. Moreover, and +unless the full path is specified, the local version of the aliroot +executable will be ignored and the official version executed. + +
Therefore in order to develop one or more packages locally +(let's say the TPC) and make modifications, the following steps should be +performed. The remote cvs server use and setup is explained in the code development section. + +
|
+ + Preparation of the environment + + | |
|---|---|
| $ mkdir AliRoot + | create the working directory + |
| $ cd AliRoot + | set default to it + |
| $ mkdir pro + | create pro subdirectory + |
| $ cd pro + | set default to it + |
| $ ln -s $ALICE_ROOT/* ./ + | link all files here + |
| $ rm lib + | remove link for library, we need a local file here to containing the new + TPC library + |
| $ rm bin + | remove bin, we need a local copy of the aliroot + executable + |
| $ mkdir bin + | make a local bin directory + |
| $ rm CVS + | remove the link to the CVS directory, we need a local one + to check-out files + |
| $ rm TPC + | remove link for TPC subdirectory, we need the real files here + |
| $ rm ALIROOT + | remove link to ALIROOT subdirectory, may be this is not really necessary + on all systems, but we do it just to be on the safe side + |
| $ cvs co -r Release-3-XX TPC + | get from the cvs server the release version of the TPC files to be + modified + |
| $ cvs co -r Release-3-XX ALIROOT + | get from the server the release version of the ALIROOT files to recreate + the executable + |
| $ mkdir -p lib/tgt_$ALICE_TARGET + | create library directory + |
| $ cd lib/tgt_$ALICE_TARGET + | set default to the lib directory + |
| $ ln -s $ALICE_ROOT/lib/tgt_$ALICE_TARGET/* ./ + | link all libraries here + |
| $ rm libTPC.sl (on HP)
+ $ rm libTPC.so (on the other systems) + | remove link to TPC library, we need a real one + |
| $ changeRoot $HOME/AliRoot + | change the AliRoot root to $HOME/AliRoot via the changeRoot command + |
| $ rehash + | make sure that the new PATH is taken into account by the shell + |
|
+ + Normal development cycle + + | |
| $ cd $ALICE_ROOT/TPC + | (1) set default to TPC directory + |
| $ make macroclean + | clean up all objects + |
| $ emacs AliTPCv1.cxx + | (2) edit all the files... + |
| $ make + | (3) recreate ../lib/libTPC.sl + |
| $ cd ../ALIROOT + | set default to ALIROOT directory + |
| $ make macroclean + | clean up object files + |
| $ make + | make new executable + |
| $ cd directory + | (4) set default elsewhere + |
| $ aliroot + | (5) run aliroot + |
|
+ + | |
Steps 1-5 are the normal development cycle after the first pass through the +procedure. +