Difference between revisions of "Documentation/Nightly/Developers/Extensions/DescriptionFile"
From Slicer Wiki
m |
m |
||
Line 58: | Line 58: | ||
<tr> | <tr> | ||
<td><code>depends</code></td> | <td><code>depends</code></td> | ||
− | <td>List of extensions required to build this extension. Specify <code>"NA"</code> if there are no dependency.</td> | + | <td>List of extensions required to build this extension. Specify <code>"NA"</code> if there are no dependency.<br>Extension names should be separated by a single space. For example: <code>extensionA extensionB</code></td> |
<td></td> | <td></td> | ||
</tr> | </tr> |
Revision as of 04:46, 19 June 2015
Home < Documentation < Nightly < Developers < Extensions < DescriptionFile
For the latest Slicer documentation, visit the read-the-docs. |
Extension description file
An extension description file is a text file with s4ext
extension allowing to specify metadata associated with an extension.
- A metadata is specified using a keyword followed by at least one spaces and the associated value.
- Multiline value are not supported.
- Empty line are ignored
- Line starting with a
#
will be considered as comment.
This file is generated by the build system in the extension build tree. It can also be generated by the ExtensionWizard using the extension metadata reported in the extension CMakeLists.txt
The following code block illustrates how comments, metadata and associated value can be specified:
# This is a comment metadataname This is the value associated with 'metadataname' # This is an other comment anothermetadata This is the value associated with 'anothermetadata'
Supported metadata
[1] Parameter like &foo=bar
are not supported. Use an url shortener.
Partially supported metadata
Name | Description |
---|---|
status |
Give people an idea what to expect from this code |