| 26 |
|
<p> |
| 27 |
|
To define a new project you need to specify three sets of configuration files |
| 28 |
|
corresponding to the areas of distribution, configuration and the build system. |
| 29 |
< |
Configuration files are written as XML like documents called <a href=ActiveDoc.html>ActiveDocs</a>. |
| 29 |
> |
Configuration files are written as XML-like documents called <a href=ActiveDoc.html>ActiveDocs</a>. |
| 30 |
|
<p> |
| 31 |
– |
<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 |
| 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 |
| 39 |
|
configuration files by naming a <em>configuration directory</em> and a |
| 40 |
|
<em>Requirements Document</em> |
| 41 |
+ |
|
| 42 |
|
<li>You describe the configuration profile in a <a href=requirementdoc.html>Requirements Document</a> |
| 43 |
|
This document will tell SCRAM what to put in your projects toolbox. You will only be able to use |
| 44 |
|
tools in this toolbox. In your configuration directory you will also need to specify the |
