Documentation/Nightly/Developers/Build ExtensionsIndex
From Slicer Wiki
Revision as of 17:47, 12 June 2013 by JChris.FillionR (talk | contribs) (Created page with '== Overview == Locally building an extension index provides a convenient way to: * check [[Documentation/{{documentation/version}}/Developers/Extensions/DescriptionFile|extensi…')
Home < Documentation < Nightly < Developers < Build ExtensionsIndex
Overview
Locally building an extension index provides a convenient way to:
- check extension description files are valid
- upload one or more extensions at ones to check that Slicer can download and install them
Given a directory containing one or more extension description files, it is possible to manually configure and build the associated extensions specifying the following CMake options:
Slicer_DIR |
Path to Slicer build tree |
Slicer_EXTENSION_DESCRIPTION_DIR |
Path to folder containing extension description files |
Optionally, it is also possible to specify:
CMAKE_BUILD_TYPE |
On unix-like platform, should match the build type of the associated Slicer build directory |
Slicer_UPLOAD_EXTENSIONS |
By default set to OFF .If enabled, extension builds will be submitted to Slicer dashboard and associated packages will be uploaded to extensions server |
MIDAS_PACKAGE_URL |
MIDAS extensions server URL specifying where the extension should be uploaded. For example http://slicer.kitware.com/midas3 |
MIDAS_PACKAGE_EMAIL |
Email allowing to authenticate to the extensions server. |
MIDAS_PACKAGE_API_KEY |
Token allowing to authenticate to the extensions server. |
TBD