| 1 |
williamc |
1.1 |
<! Style Sheet Header>
|
| 2 |
|
|
<html>
|
| 3 |
|
|
<head>
|
| 4 |
|
|
<title>project.html</title>
|
| 5 |
williamc |
1.3 |
<body bgcolor=beige>
|
| 6 |
williamc |
1.1 |
<! End Style Sheet Header -----------Insert Text Here --------------------->
|
| 7 |
|
|
<center>
|
| 8 |
|
|
<h1>Installing a Project Using SCRAM</h1>
|
| 9 |
williamc |
1.3 |
<font color=red>S</font>oftware <font color=red>C</font>onfiguration,
|
| 10 |
|
|
<font color=red>R</font>elease <font color=red>A</font>nd
|
| 11 |
|
|
<font color=red>M</font>anagement
|
| 12 |
williamc |
1.1 |
</center>
|
| 13 |
|
|
<hr>
|
| 14 |
williamc |
1.3 |
It is envisaged that releases of a project need to be distributed to remote
|
| 15 |
|
|
sites. The release is contained in a special scram area which is created
|
| 16 |
|
|
by scram according to the projects requirements. Once a carbon copy of the area
|
| 17 |
|
|
has been built on the remote site, the adminisatrator can "scram install" it
|
| 18 |
|
|
into the remote sites scram database. Once installed many other scram
|
| 19 |
|
|
development areas can be based upon it, for use both other users,developers etc.
|
| 20 |
|
|
<p>
|
| 21 |
williamc |
1.1 |
SCRAM aims to make installion of projects as painless a possible.
|
| 22 |
|
|
It is designed to be used
|
| 23 |
|
|
with a web browser so that you simply click on a link to start the installation
|
| 24 |
|
|
process.
|
| 25 |
|
|
<p>
|
| 26 |
|
|
You will be asked questions about your system as required by the project during
|
| 27 |
|
|
the installation. Some error and consistency checking is provided
|
| 28 |
|
|
(but is still in its infancy so dont expect anything too fancy).
|
| 29 |
williamc |
1.3 |
You can change these values later (see below)
|
| 30 |
|
|
so dont worry too much if you get things wrong at this stage.
|
| 31 |
williamc |
1.1 |
<p>
|
| 32 |
|
|
Once through the installation process you can make the project available for
|
| 33 |
williamc |
1.3 |
general use by using the <em>scram install</em> command. This command will
|
| 34 |
williamc |
1.1 |
update your local SCRAM database with the project details so that other
|
| 35 |
|
|
SCRAM user can simply refer to it by name.
|
| 36 |
sashby |
1.5 |
|
| 37 |
|
|
<p>
|
| 38 |
|
|
|
| 39 |
|
|
<h2>Automated setup procedure for new project areas</h2>
|
| 40 |
|
|
The setup procedure is first invoked for a new project area to set up the tools selected via the
|
| 41 |
|
|
RequirementsDoc. This is now automated by using site information read from a configuration file.
|
| 42 |
|
|
The configuration file is called cmstools-SITENAME.conf, where SITENAME is the name of your
|
| 43 |
|
|
site (the default is CERN). The sitename can be changed by modifying the file <em>sitename</em>.
|
| 44 |
|
|
These files reside in the configuration area for each SCRAM-based project under
|
| 45 |
|
|
a subdirectory <em>site</em>. The configuration file contains default paths to tools,
|
| 46 |
|
|
especially ANAPHE tools, which scram will use first to find locations of libraries and
|
| 47 |
|
|
include files.
|
| 48 |
|
|
Here is an extract from the CERN configuration file:
|
| 49 |
|
|
<pre>
|
| 50 |
|
|
|
| 51 |
|
|
###############################################################
|
| 52 |
|
|
# cmstools-CERN.conf #
|
| 53 |
|
|
###############################################################
|
| 54 |
|
|
# modified : Tue Nov 20 11:39:49 2001 / SFA #
|
| 55 |
|
|
# : #
|
| 56 |
|
|
# : #
|
| 57 |
|
|
# function : Configuration file for setting up ANAPHE and CMS #
|
| 58 |
|
|
# : tools at CERN. #
|
| 59 |
|
|
# : #
|
| 60 |
|
|
###############################################################
|
| 61 |
|
|
# Set some ANAPHE variables.
|
| 62 |
|
|
# Specify the OS. All subsequent defns will be for this OS:
|
| 63 |
|
|
ANAPHEOS:Linux
|
| 64 |
|
|
# ANAPHE version:
|
| 65 |
|
|
ANAPHEVER:3.6.2
|
| 66 |
|
|
# Specify the top of the ANAPHE tool dir, excluding the version:
|
| 67 |
|
|
ANAPHETOP:/afs/cern.ch/sw/lhcxx/specific/redhat61/gcc-2.95.2
|
| 68 |
|
|
#
|
| 69 |
|
|
CMSTOOL:g77:
|
| 70 |
|
|
+FC:/usr/local/gcc-alt-2.95.2/bin/g77
|
| 71 |
|
|
CMSTOOL:gcc:
|
| 72 |
|
|
+CXX:/usr/local/gcc-alt-2.95.2/bin/c++
|
| 73 |
|
|
+CC:/usr/local/gcc-alt-2.95.2/bin/gcc
|
| 74 |
|
|
+LD_LIBRARY_PATH:/usr/local/gcc-alt-2.95.2/lib
|
| 75 |
|
|
CMSTOOL:htl:
|
| 76 |
|
|
+SCHEMA_HOME:/afs/cern.ch/sw/lhcxx/share/HTL/1.3.1.1/schema
|
| 77 |
|
|
CMSTOOL:zlib:
|
| 78 |
|
|
+ZLIB_BASE:/afs/cern.ch/cms/Releases/sw/zlib/Linux__2.0/zlib-1.1.3
|
| 79 |
|
|
# Specify the OS. All subsequent defns will be for this OS:
|
| 80 |
|
|
ANAPHEOS:SunOS
|
| 81 |
|
|
# ANAPHE version:
|
| 82 |
|
|
ANAPHEVER:3.6.2
|
| 83 |
|
|
# Specify the top of the ANAPHE tool dir, excluding the version:
|
| 84 |
|
|
ANAPHETOP:/afs/cern.ch/sw/lhcxx/specific/sun4x_57/CC-5.2
|
| 85 |
|
|
#
|
| 86 |
|
|
CMSTOOL:f77:
|
| 87 |
|
|
+FC:/afs/cern.ch/project/sun/solaris/opt/SUNWspro61/bin/f77
|
| 88 |
|
|
CMSTOOL:cc:
|
| 89 |
|
|
+CXX:/afs/cern.ch/project/sun/solaris/opt/SUNWspro61/bin/CC
|
| 90 |
|
|
+CC:/afs/cern.ch/project/sun/solaris/opt/SUNWspro61/bin/cc
|
| 91 |
|
|
+CXX_PRIOR_LIBS:/afs/cern.ch/project/sun/solaris/opt/SUNWspro61/WS6U1/lib
|
| 92 |
|
|
CMSTOOL:htl:
|
| 93 |
|
|
+SCHEMA_HOME:/afs/cern.ch/sw/lhcxx/share/HTL/1.3.1.1/schema
|
| 94 |
|
|
CMSTOOL:zlib:
|
| 95 |
|
|
+ZLIB_BASE:/afs/cern.ch/cms/Releases/sw/zlib/SunOS__5.6/zlib-1.1.3
|
| 96 |
|
|
|
| 97 |
|
|
</pre>
|
| 98 |
|
|
|
| 99 |
|
|
For ANAPHE tools under linux, the default path is ANAPHETOP and normally the libraries are
|
| 100 |
|
|
found under a subdirectory matching the ANAPHE version (set using the variable ANAPHEVER
|
| 101 |
|
|
in the above file).
|
| 102 |
|
|
If a tool is not likely to be found under this default path, an entry is made in the file.
|
| 103 |
|
|
This entry begins with CMSTOOL and the tool name (as known to scram), and any variables
|
| 104 |
|
|
that scram must set for this tool are subsequently listed, each entry beginning
|
| 105 |
|
|
with a plus sign.
|
| 106 |
|
|
<p>
|
| 107 |
|
|
When setting up the tools, scram reads this file and creates a lookup-table. If the default search fails,
|
| 108 |
|
|
scram looks for an entry in the lookup table for the tool. If an entry exists, subsequent
|
| 109 |
|
|
values for the scram variables will be used. If no entry is found, scram will drop to an interactive
|
| 110 |
|
|
environment and request user input.
|
| 111 |
|
|
|
| 112 |
williamc |
1.1 |
<p>
|
| 113 |
williamc |
1.2 |
<h2>Changing Installation Defaults</h2>
|
| 114 |
williamc |
1.3 |
You can use the <P>
|
| 115 |
|
|
<b>scram setup [-i] <em>toolname [[version] [file]]</em></b><p>
|
| 116 |
|
|
command to rerun the installation of a specific tool.<p>
|
| 117 |
|
|
You can override the automatic mechanisms that
|
| 118 |
|
|
SCRAM uses to install a tool with the <b>-i</b> option
|
| 119 |
|
|
<br>
|
| 120 |
|
|
If the setup command is not sufficient you
|
| 121 |
|
|
can modify the values directly. Simply edit the appropriate <em>.dat</em> file
|
| 122 |
williamc |
1.2 |
in the .SCRAM/<em>architecture_specific</em> directory from the top of the
|
| 123 |
|
|
project installation.
|
| 124 |
williamc |
1.1 |
<! Style Sheet Footer ---------------Do not change anything after this line-->
|
| 125 |
|
|
<hr>
|
| 126 |
|
|
<table border=1 width=100%>
|
| 127 |
|
|
<td align=left>
|
| 128 |
sashby |
1.4 |
<a href=mailto:Shaun.Ashby@cern.ch
|
| 129 |
|
|
>Shaun Ashby</a>
|
| 130 |
williamc |
1.1 |
</td>
|
| 131 |
|
|
<td align=center>
|
| 132 |
|
|
<script language="JavaScript">
|
| 133 |
|
|
<!---//hide script from old browsers
|
| 134 |
|
|
document.write( "<br>Last updated "+ document.lastModified
|
| 135 |
|
|
);
|
| 136 |
|
|
//end hiding contents --->
|
| 137 |
|
|
</script>
|
| 138 |
|
|
</td>
|
| 139 |
|
|
<td align=right>Show <a href=/cgi-cmc/pagestat>Stats</a>
|
| 140 |
|
|
</td>
|
| 141 |
|
|
</table>
|
| 142 |
|
|
</body> </html>
|
| 143 |
|
|
<! End Style Sheet Footer>
|
