<HTML>
<HEAD>
<TITLE>Installation</TITLE>
+
<link rev="made" href="mailto:Federico.Carminati@cern.ch">
-<STYLE>
+<link rel="stylesheet" href="http://www.w3.org/StyleSheets/Core/Swiss" type="text/css">
+<STYLE type="text/css">
+
BODY {
background: #FFFFFF;
}
background: #FFFFFF;
}
+TABLE.wide {
+ cellspacing: 100%;
+ background: #FF0000
+ }
+
</STYLE>
-<link rel="stylesheet" href="http://www.w3.org/StyleSheets/Core/Swiss" type="text/css">
</HEAD>
-<BODY background=#FFFFFF>
+<BODY>
<TABLE>
<TR>
<TD><img src="picts/MadHatter.gif" alt="ALICE Off-line Project Logo">
</TR>
</TABLE>
-<h2>Installation</h2>
+<H2><A NAME="#Content">Content</A></H2>
+<UL>
+<LI><A HREF="#Installation">Installation</A>
+<LI><A HREF="#Code">Code development and user environment</A>
+</UL>
+
+<HR>
+
+<h2><A HREF="#Content" NAME="Installation">Installation</A></h2>
+
<ol>
<p><li> Install <a href="http://root.cern.ch">ROOT</a> and define the
</table>
<p> <i>MM.mm-pp</i> is the number of the latest <i>M</i>ajor and
-<i>m</i>inor version and the <i>p</i>atch 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:
+<i>m</i>inor version and the <i>p</i>atch number. The file(s) have to be
+unpacked into the $ALICE directory via the command:
<p><pre>$ gtar xvfz Ali[...].tar.gz</pre>
CERN (1.09) does not support well binary files. Therefore some data files
will be missing with this download mechanism, and these will have to be
fetched <em>by hand</em>. The setup of the access to the remote cvs server
-is described in the <a href="management.html">Code Management</a> section. The
+is described in the Code Development section. The
code is dowloaded via the command:
<p><pre>
$ cd $ALICE
-$ cvsa co -d pro AliRoot
+$ cvsa co -r Release-3-02 -d pro AliRoot
</pre>
</ul>
<p><li>Copy the file $ALICE_ROOT/.rootrc to your home directory
+<p><li>For users with c-like shells, update your search path:
+
+<p>
+<pre>
+$ rehash
+</pre>
+
+<p>This usually has to be done only once, after having defined the new PATH.
+
<p><li>Change to your home directory and run the code
<p>
</pre>
</ol>
-<h2>Code development and user environment</h2>
+<h2><A HREF="#Content" NAME="Code">Code development and user environment</A></h2>
<p>If the ALICE environment is set up correctly, the
<var>$ALICE_ROOT/lib/tgt_$ALICE_TARGET</var> directory is in the shared
<p>Therefore in order to develop one or more packages locally
(let's say the TPC) and make modifications, the following steps should be
performed. We suppose here that the remote cvs server has been setup correctly
-as explained in the <a href="management.html">code management</a> section.
-
-<p><table>
+as explained in the <a href="../development.html">code development</a> section.
+
+<p><table id="wide" cellspacing=10%>
+ <tr align=center>
+ <th colspan=2>
+ <hr><br>
+ <font size=+1>Preparation of the environment</font>
+ <br><hr>
<tr align=left>
<th width=30%>$ mkdir AliRoot
<td width=50%>create the working directory
<th>$ ln -s $ALICE_ROOT/lib/* ./
<td>link all libraries here
<tr align=left>
- <th>$ rm libTPC.sl
+ <th>$ rm libTPC.sl (on HP)
+ <br>$ rm libTPC.so (on the other systems)
<td>remove link to TPC library, we need a real one
<tr align=left>
<th>$ changeRoot $HOME/AliRoot
- <td>change the AliRoot root to $HOME/AliRoot
+ <td>change the AliRoot root to $HOME/AliRoot via the <em>changeRoot</em> command
<tr align=left>
<th>$ rehash
<td>make sure that the new PATH is taken into account by the shell
+ <tr align=center>
+ <th colspan=2>
+ <hr><br>
+ <font size=+1>Normal development cycle</font>
+ <br><hr>
<tr align=left>
<th>$ cd $ALICE_ROOT/TPC
<td>(1) set default to TPC directory
<tr align=left>
<th>$ aliroot
<td>(5) run aliroot
+ <tr align=center>
+ <th colspan=2>
+ <hr>
</table>
<p>Steps 1-5 are the normal development cycle after the first pass through the
git://git.uio.no / u / mrichter / AliRoot.git / blobdiff