Difference between revisions of "Documentation/Nightly/Developers/Extensions/Index"
m (Created page with 'Think of the ExtensionsIndex as a repository containing a list of [http://todo extension description file]s (*.s4ext) used by the Slicer [[Documentation/{{documentation/version}}…') |
(Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887) |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | Think of the ExtensionsIndex as a repository containing a list of [ | + | <noinclude>{{documentation/versioncheck}}</noinclude> |
| + | Think of the ExtensionsIndex as a repository containing a list of [[Documentation/{{documentation/version}}/Developers/Extensions/DescriptionFile|extension description file]]s <code>*.s4ext</code> used by the Slicer [[Documentation/{{documentation/version}}/Developers/Extensions/BuildSystem|extensions build system]] to build, test, package and upload [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s on the [[Documentation/{{documentation/version}}/Developers/Extensions/Server|extensions server]]. | ||
| − | Once uploaded on an [[Documentation/{{documentation/version}}/Developers/Extensions/Server|extensions server]], within Slicer, [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s can be | + | Once uploaded on an [[Documentation/{{documentation/version}}/Developers/Extensions/Server|extensions server]], within Slicer, [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s can be installed using the [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager|extensions manager]]. |
The [[Documentation/{{documentation/version}}/Extensions/Catalog|extensions catalog]] provides Slicer users with a convenient way to access the [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s previously uploaded. | The [[Documentation/{{documentation/version}}/Extensions/Catalog|extensions catalog]] provides Slicer users with a convenient way to access the [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s previously uploaded. | ||
| + | |||
| + | There are multiple branches on the ExtensionsIndex: | ||
| + | |||
| + | * <code>master</code>: This branch contain description files of extensions that will be built against Slicer nightly. | ||
| + | * [...] | ||
| + | * <code>{{documentation/currentversion}}</code>: This branch contain description files of extensions that will be built against latest Slicer {{documentation/currentversion}} available patch release. | ||
| + | |||
| + | The reasoning behind this approach is that since both the Slicer API and ABI associated with Slicer base libraries are changing often, compatibility of the extensions available for download is guaranteed by building extensions against every Slicer revisions. | ||
| + | |||
| + | It means that developer willing to have their extensions available on the different versions of Slicer will have to submit pull requests for each version. | ||
Revision as of 08:00, 14 June 2013
Home < Documentation < Nightly < Developers < Extensions < Index
|
For the latest Slicer documentation, visit the read-the-docs. |
Think of the ExtensionsIndex as a repository containing a list of extension description files *.s4ext used by the Slicer extensions build system to build, test, package and upload extensions on the extensions server.
Once uploaded on an extensions server, within Slicer, extensions can be installed using the extensions manager.
The extensions catalog provides Slicer users with a convenient way to access the extensions previously uploaded.
There are multiple branches on the ExtensionsIndex:
master: This branch contain description files of extensions that will be built against Slicer nightly.- [...]
4.10: This branch contain description files of extensions that will be built against latest Slicer 4.10 available patch release.
The reasoning behind this approach is that since both the Slicer API and ABI associated with Slicer base libraries are changing often, compatibility of the extensions available for download is guaranteed by building extensions against every Slicer revisions.
It means that developer willing to have their extensions available on the different versions of Slicer will have to submit pull requests for each version.
