| 1 |
williamc |
1.1.2.1 |
<! Style Sheet Header>
|
| 2 |
|
|
<html>
|
| 3 |
|
|
<head>
|
| 4 |
|
|
<title>projectconfig.html</title>
|
| 5 |
|
|
<body bgcolor=beige>
|
| 6 |
|
|
<! End Style Sheet Header -----------Insert Text Here --------------------->
|
| 7 |
|
|
<center>
|
| 8 |
williamc |
1.1.2.4.2.1.4.1 |
<h2>Defining SCRAM Projects</h2>
|
| 9 |
williamc |
1.1.2.1 |
<p>
|
| 10 |
|
|
<font color=red>S</font>oftware <font color=red>C</font>onfiguration,
|
| 11 |
|
|
<font color=red>R</font>elease <font color=red>A</font>nd
|
| 12 |
|
|
<font color=red>M</font>anagement
|
| 13 |
|
|
</center>
|
| 14 |
|
|
<hr>
|
| 15 |
williamc |
1.1.2.4.2.1.4.1 |
<h1>Quick Links</h1>
|
| 16 |
williamc |
1.1.2.1 |
<ul>
|
| 17 |
williamc |
1.1.2.4.2.1 |
<li><a href=ActiveDoc.html>The ActiveDoc System</a>
|
| 18 |
|
|
<li><a href=bootstrap.html>The BootStrap ActiveDoc</a>
|
| 19 |
|
|
<li><a href=requirementdoc.html>The Requirements ActiveDoc</a>
|
| 20 |
williamc |
1.1.2.2 |
<li><a href=versiondefs.html>Overidding Default Versions</a>
|
| 21 |
williamc |
1.1.2.3 |
<li><a href=configBuildFile.html>The Project BuildFiles</a>
|
| 22 |
williamc |
1.1.2.1 |
</ul>
|
| 23 |
williamc |
1.1.2.4.2.1.4.1 |
<h1>Elements of a SCRAM project</h1>
|
| 24 |
|
|
<img src=../images/project.jpg>
|
| 25 |
|
|
<p>
|
| 26 |
|
|
To define a new project you need to specify three sets of configuration files
|
| 27 |
|
|
corresponding to the areas of distribution, configuration and the build system.
|
| 28 |
|
|
Configuration files are written as XML like documents called <a href=ActiveDoc.html>ActiveDocs</a>.
|
| 29 |
|
|
<p>
|
| 30 |
|
|
<b>
|
| 31 |
|
|
<ol>
|
| 32 |
|
|
<li>Project Structure and Distribution is described by a <a href=bootstrap.html>BootStrap Document</a><br>
|
| 33 |
|
|
There should be at least one bootstrap document for each project. Any number of others can be added to
|
| 34 |
|
|
describe different distributions and access methods.
|
| 35 |
|
|
e.g. a developers distribution may contain the full source code
|
| 36 |
|
|
whereas a users distribution may just contain the header files, and a release distributed via a cd
|
| 37 |
|
|
will require a different BootStrap to one intended for downloading everything from the internet.<br>
|
| 38 |
|
|
The BootStrap file will also tell SCRAM where to find all the other configuration files.
|
| 39 |
|
|
<li>You describe the configuration profile in a <a href=requirementdoc.html>Requirements Document</a>
|
| 40 |
|
|
This document will tell SCRAM what to put in your projects toolbox. You will only be able to use
|
| 41 |
|
|
tools in this toolbox. In your configuration directory you will also need to specify the
|
| 42 |
|
|
specific SCRAM version you are using by creating a <a href=http://cmsdoc.cern.ch/Releases/SCRAM/V0_16branch/doc/html/versionsel.html#Auto>scram_version</a> file
|
| 43 |
|
|
<li>The <a href=configBuildFile.html>Project BuildFiles</a> tells the scram
|
| 44 |
|
|
build system how to construct your project
|
| 45 |
|
|
</ol>
|
| 46 |
williamc |
1.1.2.1 |
<! Style Sheet Footer ---------------Do not change anything after this line-->
|
| 47 |
|
|
<hr>
|
| 48 |
|
|
<table border=1 width=100%>
|
| 49 |
|
|
<td align=left>
|
| 50 |
|
|
<a href=mailto:Christopher.Williams@cern.ch
|
| 51 |
|
|
>Chris Williams</a>
|
| 52 |
|
|
</td>
|
| 53 |
|
|
<td align=center>
|
| 54 |
williamc |
1.1.2.4 |
Last Updated Thu Jun 15 18:43:20 2000
|
| 55 |
williamc |
1.1.2.1 |
</td>
|
| 56 |
|
|
<td align=right><a href=/cgi-cmc/pagestat>Show Stats</a>
|
| 57 |
|
|
</td>
|
| 58 |
|
|
</table>
|
| 59 |
|
|
</body> </html>
|
| 60 |
|
|
<! End Style Sheet Footer>
|
