| 74 |
|
Once it is tested and the tool is to be made available to the entire project, |
| 75 |
|
its name/url should be added to the 'project requirements' file via the |
| 76 |
|
<Require > tag.<br> |
| 77 |
– |
<em>Current limitations</em><br> |
| 78 |
– |
The url mechanism is limited to a simple toolname which corresponds to a file |
| 79 |
– |
in the current SCRAM toolbox area. <br> |
| 80 |
– |
Future developments will allow any url (e.g file:, http:) to be specified. |
| 81 |
– |
This will allow description files to be stored anywhere on the net for use |
| 82 |
– |
between different projects that use the same external product. |
| 77 |
|
<p> |
| 78 |
|
Specifying a product to be used once its installed can be done via the |
| 79 |
< |
BuildFile and a special <External name=<em>toolname</em>> tag. This will |
| 86 |
< |
soon be depreciated to simplyfy the interface to be replaced with the |
| 87 |
< |
<Use external=> tag. |
| 79 |
> |
BuildFile and a special <External name=<em>toolname</em>> tag. |
| 80 |
|
</td> |
| 81 |
|
</tr> |
| 82 |
|
<tr> |
| 136 |
|
</td> |
| 137 |
|
<td> |
| 138 |
|
Multiple platforms are supported. Choice of compilers etc. is made at the |
| 139 |
< |
project level. Compiler types/QA tool are currently hardcoded in although |
| 140 |
< |
future developments will require a tool description file for each |
| 149 |
< |
so that any such tool can be easily installed/used with the scram setup |
| 150 |
< |
command as with any other external product. |
| 139 |
> |
project level. Compiler types/QA tools can be included with a Tool description |
| 140 |
> |
file. |
| 141 |
|
</td> |
| 142 |
|
</tr> |
| 143 |
|
<tr> |
