Athena Developer Guide
Athena Developer Guide
Athena Developer Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Athena</strong> Chapter 4 Establishing a development environment Version/Issue: 2.0.0<br />
4.2.2 Commands to establish a c-shell or varient login environment<br />
The commands in Listing 4.2 establish a minimal login environment using the c-shell or varients (csh,<br />
tcsh, etc.) and should be entered into the .login file.<br />
Listing 4.2 C shell and varients commands to establish an ATLAS login environment<br />
setenv ATLAS_ROOT /afs/cern.ch/atlas<br />
setenv CVSROOT :kserver:atlas-sw.cern.ch:/atlascvs<br />
if ( $?PATH ) then<br />
setenv PATH ${PATH}:$ATLAS_ROOT/software/bin<br />
else<br />
setenv PATH $ATLAS_ROOT/software/bin<br />
endif<br />
source ‘srt setup -s csh‘<br />
4.3 Using SRT to checkout ATLAS software packages<br />
ATLAS software is organized as a set of hierarchical packages, each package corresponding to a logical<br />
grouping of (typically) C++ classes. These packages are kept in a centralized code repository, managed<br />
by CVS [Ref]. Self-contained snaphots of the package hierarchy are created at frequent intervals, and<br />
executables and libraries are created from them. These snapshots are termed releases, and in many<br />
cases users can execute applications directly from a release of their choice. Each release is identified by<br />
a three-component identifier of the form ii.jj.kk (e.g. 1.3.2).<br />
page 22
Change language