| 11 |
|
<font color=red>M</font>anagement |
| 12 |
|
</center> |
| 13 |
|
<hr> |
| 14 |
< |
<ol> |
| 15 |
< |
<li><h2>Online help</h2> |
| 16 |
< |
Help is available through the use of the help command. |
| 17 |
< |
<p>e.g.<br> |
| 14 |
> |
<p> |
| 15 |
> |
This page contains some useful information for developers using SCRAM, including how to set |
| 16 |
> |
up a private developer area and how to get more help.<p> |
| 17 |
> |
<p> |
| 18 |
> |
<h2>Online help</h2> |
| 19 |
> |
Help is available through the use of the global help command, or more specifically for |
| 20 |
> |
individual commands. <p>For example: |
| 21 |
> |
<p> |
| 22 |
|
<table> |
| 23 |
|
<tr> |
| 24 |
|
<td> |
| 25 |
< |
<font size=-1><b> |
| 22 |
< |
scram help</b></font></td><td>will list the available scram commands</td> |
| 25 |
> |
<font size=3><pre>scram help</pre></font></td><td> will list the available scram commands</td> |
| 26 |
|
</tr> |
| 27 |
|
<tr> |
| 28 |
|
<td> |
| 29 |
< |
<font size=-1> |
| 27 |
< |
<b>scram <em>command</em> help</b></font></td> |
| 28 |
< |
<td> will list the help for that command</td> |
| 29 |
> |
<font size=3><pre>scram <em>command</em> help</pre></font></td><td> will list the help for a specific command</td> |
| 30 |
|
</tr> |
| 31 |
|
<tr> |
| 32 |
|
<td> |
| 33 |
< |
<font size=-1> |
| 33 |
< |
scram build help </font></td><td>Not working right now, but should list |
| 34 |
< |
the available types of build you can perform in that location</td> |
| 33 |
> |
<font size=3><pre>scram build help</pre></font></td><td> will list the available types of build you can perform in that location</td> |
| 34 |
|
</tr> |
| 35 |
|
</table> |
| 36 |
|
<p> |
| 37 |
< |
<li><h2>Development Spaces</h2> |
| 37 |
> |
<h2>Development Spaces</h2> |
| 38 |
> |
|
| 39 |
|
<h3>What are Development Spaces?</h3> |
| 40 |
+ |
|
| 41 |
|
A development space is an isolated area that you can use to work on a |
| 42 |
|
given project without affecting anyone else. This development space is |
| 43 |
|
associated with a specific installation of the project from which it can |
| 47 |
|
if it cannot find appropriate versions in the central installation. |
| 48 |
|
|
| 49 |
|
<h3>Creating Your Local Development Space</h3> |
| 50 |
+ |
|
| 51 |
|
To develop on a given project you first need to have a copy of the project |
| 52 |
|
installed at your site on which to base your development area. |
| 53 |
< |
You can see the available locally installed copies |
| 53 |
> |
You can see the available locally installed copies of projects |
| 54 |
|
with the command :<p> |
| 55 |
< |
<font size=-1><b>scram list</b></font> |
| 55 |
> |
<font size=3><pre> scram list</pre></font> |
| 56 |
|
<p> |
| 57 |
|
To create your personal space you then issue the command: |
| 58 |
|
<p> |
| 59 |
< |
<font size=-1><b> |
| 60 |
< |
scram project <em>project_name</em> <em>project_version</em> |
| 61 |
< |
</b> |
| 59 |
> |
<font size=3><pre> |
| 60 |
> |
scram project <em>project_name</em> <em>project_version</em> |
| 61 |
> |
</pre> |
| 62 |
|
</font> |
| 63 |
|
<p> |
| 64 |
|
Where <em>project_name</em> and <em>project_version</em> correspond to those |
| 65 |
< |
available from the <font size=-1><b>scram list</b></font> command. |
| 66 |
< |
<p> |
| 65 |
> |
available from the project list. |
| 66 |
> |
<br> |
| 67 |
|
The development area will reflect the structure and will have the same |
| 68 |
|
build environment as the base project specified. |
| 69 |
|
<p> |
| 70 |
< |
<li><h2>Using The Development Area</h2> |
| 70 |
> |
|
| 71 |
> |
|
| 72 |
> |
<h2>Using The Development Area</h2> |
| 73 |
> |
|
| 74 |
|
Assuming you are at the top of your new development area: |
| 75 |
+ |
<p> |
| 76 |
|
<table border=0> |
| 77 |
|
<tr> |
| 78 |
|
<td> |
| 79 |
< |
<font size=-1> |
| 80 |
< |
<b>cd src</font></b></td><td> goto the src directory</td></tr> |
| 79 |
> |
<font size=3> |
| 80 |
> |
<b>cd src</font></b></td><td>-change to the src directory</td></tr> |
| 81 |
|
<tr> |
| 82 |
< |
<td valign=top><font size=-1> |
| 82 |
> |
<td valign=top><font size=3> |
| 83 |
|
<b>cvs co <em>module</em></b> (e.g. for cvs based projects)</font></td> |
| 84 |
< |
<td>Check out whatever module you require. As an example, you may wish to |
| 84 |
> |
<td>-check out whatever module you require. As an example, you may wish to |
| 85 |
|
develop a module that corresponds to a library. You will need to check-out the |
| 86 |
|
entire module, rather than just the files your working on, as the library |
| 87 |
|
building system uses the local file list to specify the library contents. |
| 88 |
|
<p> |
| 89 |
< |
Once checked out you can cd into the module and edit the files as |
| 89 |
> |
-once checked out you can cd into the module and edit the files as |
| 90 |
|
required. |
| 91 |
|
<p><em><b>Note</b> The cvs co command above will give you the development head. |
| 92 |
|
If you wish to use a fixed tagged version or the head of a different |
| 93 |
|
development branch you must specify this with the -r option to cvs. |
| 94 |
|
<p> |
| 95 |
< |
e.g. <font size=-1><b>cvs co -r beta <em>module</em></b> |
| 96 |
< |
</font> |
| 91 |
< |
<p> |
| 95 |
> |
e.g. <font size=2><b>cvs co -r beta <em>module</em></b></font> |
| 96 |
> |
<br> |
| 97 |
|
</td> |
| 98 |
|
</tr> |
| 99 |
< |
<td valign=top><font size=-1> |
| 99 |
> |
<td valign=top><font size=3> |
| 100 |
|
<b> |
| 101 |
|
scram build</b></td> |
| 102 |
|
</font> |
| 103 |
< |
<td>Will perform the default build that corresponds to the directory in which |
| 103 |
> |
<td>-perform the default build that corresponds to the directory in which |
| 104 |
|
you type the command.</td> |
| 105 |
|
</tr> |
| 106 |
|
</table> |
| 107 |
< |
<li><h2>Runtime Environment</h2> |
| 108 |
< |
Each project you are working on is likeley to have different and possibly |
| 109 |
< |
even conflicting Environmental requirements during both runtime and build time. |
| 110 |
< |
SCRAM automatically takes care of the buildtime environment, however it is |
| 111 |
< |
unable to set your runtime environment for you. It can however tell you what |
| 107 |
> |
|
| 108 |
> |
<h2>Runtime Environment</h2> |
| 109 |
> |
|
| 110 |
> |
Each project you are working on is likely to have different and possibly |
| 111 |
> |
even conflicting environmental requirements during both runtime and build time. |
| 112 |
> |
SCRAM automatically takes care of the buildtime environment, though it is |
| 113 |
> |
unable to set your runtime environment for you. It can, however, tell you what |
| 114 |
|
the runtime environment should be for any given project. To see the |
| 115 |
< |
required environment simply issue the <p> |
| 116 |
< |
<font size=-1><b>scram runtime [-csh|-sh]</b></font> |
| 115 |
> |
required environment, simply issue the command<p> |
| 116 |
> |
<font size=3><pre> scram runtime [-csh|-sh]</pre></font> |
| 117 |
|
<p> |
| 118 |
< |
command from anywhere in a development space. Use the command<p> |
| 119 |
< |
<font size=-1><b>scram runtime help</b></font> |
| 118 |
> |
from anywhere in a development space. Use the command<p> |
| 119 |
> |
<font size=3><pre> scram runtime help</pre></font> |
| 120 |
|
<p> |
| 121 |
< |
for examples of use. |
| 122 |
< |
</ol> |
| 121 |
> |
for examples of usage. |
| 122 |
> |
<p> |
| 123 |
|
<! Style Sheet Footer ---------------Do not change anything after this line--> |
| 124 |
|
<hr> |
| 125 |
|
<table border=1 width=100%> |
| 126 |
|
<td align=left> |
| 127 |
< |
<a href=mailto:Christopher.Williams@cern.ch |
| 128 |
< |
>Chris Williams</a> |
| 127 |
> |
<a href=mailto:Shaun.Ashby@cern.ch |
| 128 |
> |
>Shaun Ashby</a> |
| 129 |
|
</td> |
| 130 |
|
<td align=center> |
| 131 |
|
<script language="JavaScript"> |
