Difference between revisions of "Documentation/Nightly/Developers/FAQ/Extensions"
Line 110: | Line 110: | ||
</ol> | </ol> | ||
|} | |} | ||
+ | |||
+ | == Can an extension depend on other extensions ? == | ||
+ | |||
+ | Yes. An <code>ExtensionFoo</code> can depend on <code>ExtensionBar</code> | ||
+ | |||
+ | The dependency should be specified as a list setting the variable <code>EXTENSION_DEPENDS</code> in the extension CMakeLists.txt. | ||
+ | |||
+ | For example, if you have <code>ModuleA</code>, <code>ModuleB</code> and <code>ModuleC</code> and <code>ModuleA</code> can be used as standalone one. You could create the following extensions: | ||
+ | |||
+ | * <code>Extension1</code>: <code>ModuleA</code> | ||
+ | * <code>Extension2</code>: <code>ModuleB</code>, <code>ModuleC</code> | ||
+ | |||
+ | and add the following variable to <code>Extension2/CMakeLists.txt</code>: | ||
+ | <pre> | ||
+ | set(EXTENSION_DEPENDS Extension1) | ||
+ | </pre> | ||
+ | |||
+ | '''User''': If user wants to install <code>Extension2</code>, he will be proposed to also install <code>Extension1</code>. | ||
+ | |||
+ | '''Developer''': The extension framework will build the extension in order. When building <code>Extension2</code>, it will pass the CMake option <code>-DExtension1_DIR:PATH=/path/to/Extension1-build</code>. | ||
== What are the extension specific targets: ExperimentalUpload, ExperimentalUploadOnly, ... ? == | == What are the extension specific targets: ExperimentalUpload, ExperimentalUploadOnly, ... ? == |
Revision as of 16:24, 30 May 2014
Home < Documentation < Nightly < Developers < FAQ < Extensions
For the latest Slicer documentation, visit the read-the-docs. |
Contents
- 1 Extensions
- 1.1 What is an extension description file ?
- 1.2 Can an extension contain different type of modules ?
- 1.3 Should the name of the source repository match the name of the extension ?
- 1.4 What is the Extensions Index ?
- 1.5 What is an API Key ?
- 1.6 How to obtain an API key to submit on the extension server ?
- 1.7 Where can I find the extension templates ?
- 1.8 How to build an extension ?
- 1.9 How to package an extension ?
- 1.10 How to upload an extension ?
- 1.11 Can an extension depend on other extensions ?
- 1.12 What are the extension specific targets: ExperimentalUpload, ExperimentalUploadOnly, ... ?
- 1.13 Is --launch flag available for a MacOSX installed Slicer.app ?
- 1.14 What is the difference between Documentation/Nightly/Modules and Documentation/Nightly/Extensions ?
- 1.15 Which URL should be associated with EXTENSION_HOMEPAGE metadata ?
- 1.16 How to rename an extension to add new features ?
- 1.17 How to check if an extension is built by Slicer Extensions build system ?
- 1.18 How often extensions are uploaded on the extensions server ?
- 1.19 Will an extension be uploaded if associated tests are failing ?
Extensions
What is an extension description file ?
See Description file description
Can an extension contain different type of modules ?
Yes. Extensions are used to package together all type of Slicer modules.
See also What_is_an_extension ?
Should the name of the source repository match the name of the extension ?
Assuming your extension is named AwesomeFilter
, generally, we suggest to name the extension repository either SlicerAwesomeFilter
, Slicer-AwesomeFilter
, Slicer_AwesomeFilter
, SlicerExtension-AwesomeFilter
, SlicerExtension_AwesomeFilter
.
Doing so will minimize confusion by clearly stating that the code base is associated with Slicer.
What is the Extensions Index ?
What is an API Key ?
See http://en.wikipedia.org/wiki/Application_programming_interface_key
How to obtain an API key to submit on the extension server ?
In order to upload extensions on the slicer extensions server, it is required to:
Create an account on the extension server: http://slicer.kitware.com by clicking on the
Register
link in the top right cornerGo to NA-MIC community and click on
Join community
Retrieve your API key looking at your account details:
- Go to http://slicer.kitware.com. If needed, signin by clicking on
Login
in the top right corner. - Click on your name in the top right corner.
- Click on
My account
. - Click on
API
tab. Copy the
API Key
associated withDefault
application.There is currently a bug preventing api key containing non alpanumeric characters from being used.
If your Default api key contain for example a/
, try to delete the api key and regenerate one that is not containing "/" and is namedDefault
.
We are working on the issue to update the build system so that it properly escape "/" and also get in touch with Midas team so that api key containing just number and letter are generated.
- Go to http://slicer.kitware.com. If needed, signin by clicking on
This image shows the top portion of http://slicer.kitware.com after it has been expanded by clicking the Register
button.
Where can I find the extension templates ?
The module and extension templates are available in the Slicer source tree: https://github.com/Slicer/Slicer/tree/master/Utilities/Templates/
Using the Extension Wizard, you could easily create a new extension without having to copy, rename and update manually every files.
How to build an extension ?
Assuming that the source code of your extension is located in folder MyExtension
, this could be achieved doing:
Makefile | Visual Studio |
---|---|
$ mkdir MyExtension-build $ cd MyExtension-build $ cmake -DCMAKE_BUILD_TYPE:STRING=Release -DSlicer_DIR:PATH=/path/to/Slicer-Superbuild/Slicer-build ../MyExtension $ make |
|
How to package an extension ?
Assuming your extension has been built into folder MyExtension-build
, this could be achieved doing:
Makefile | Visual Studio |
---|---|
$ make package |
|
How to upload an extension ?
If not already done, send an email on the slicer developers list asking to be granted write permission on the experimental folder.
To: slicer-devel@bwh.harvard.edu Subject: Extension NAME-OF-YOUR-EXTENSION - Asking permission to write to the Experimental folder Hi, This extension will allow to [...] Could you grant user YourUserName write access to the Experimental folder ?
Assuming your extension has been built and packaged into folder MyExtension-build
, this could be achieved by first re-configuring the project providing your midas credentials and then building the ExperimentalUploadOnly
target:
Makefile | Visual Studio |
---|---|
$ cmake -DMIDAS_PACKAGE_EMAIL:STRING=<YOUR-MIDAS-LOGIN> -DMIDAS_PACKAGE_API_KEY:STRING=<YOUR-MIDAS-APIKEY> . $ make ExperimentalUploadOnly |
|
Can an extension depend on other extensions ?
Yes. An ExtensionFoo
can depend on ExtensionBar
The dependency should be specified as a list setting the variable EXTENSION_DEPENDS
in the extension CMakeLists.txt.
For example, if you have ModuleA
, ModuleB
and ModuleC
and ModuleA
can be used as standalone one. You could create the following extensions:
Extension1
:ModuleA
Extension2
:ModuleB
,ModuleC
and add the following variable to Extension2/CMakeLists.txt
:
set(EXTENSION_DEPENDS Extension1)
User: If user wants to install Extension2
, he will be proposed to also install Extension1
.
Developer: The extension framework will build the extension in order. When building Extension2
, it will pass the CMake option -DExtension1_DIR:PATH=/path/to/Extension1-build
.
What are the extension specific targets: ExperimentalUpload, ExperimentalUploadOnly, ... ?
Slicer extension build system provides the developer with a set of convenient targets allowing to build and upload extensions.
Target name | Description |
---|---|
Experimental |
Configure, build, test the extension and publish result on CDash. |
ExperimentalUpload |
Equivalent to Experimental target followed by packaging and upload of the extension on the extension server. |
ExperimentalUploadOnly |
Only proceed to the upload of the extension on the extension server. |
test or BUILD_TESTS |
Locally execute the test |
package or PACKAGE |
Locally package the extension |
Is --launch flag available for a MacOSX installed Slicer.app ?
On MacOSx, running Slicer with the --help argument does NOT list the usual launcher related options.
$ ./Slicer.app/Contents/MacOS/Slicer --help Usage Slicer [options] Options --, --ignore-rest Ignores the rest of the labeled arguments following this flag. (default: false) -h, --help Display available command line arguments. [...] --version Displays version information and exits.
To provide some background information, when generating the package that will be distributed, an application bundle Slicer.app
is created. As explained here, a bundle is a directory with a standardized hierarchical structure that holds executable code and the resources used by that code. It means that since all libraries contained within a bundle are referenced relatively to the location of either the CLI or the Slicer executable, the use of launcher does NOT make sens.
To help fixing-up the libraries, executables and plugins so that they reference each other in a relative way, CMake provides us with the BundleUtilities module.
This module is used in two situations:
- Fixup of Slicer application itself. See SlicerCPack.cmake#L36-68 and SlicerCPackBundleFixup.cmake.in
- Fixup of an extension package. See SlicerExtensionCPack.cmake#L126-143 and SlicerExtensionCPackBundleFixup.cmake.in
What is the difference between Documentation/Nightly/Modules and Documentation/Nightly/Extensions ?
As suggested by the namespace names:
- All module documentation pages should be located under
Documentation/Nightly/Modules
- All extension documentation pages should be located under
Documentation/Nightly/Extensions
For example, if an an extension named DoSomethingGreat
bundles three modules ModuleA
, ModuleB
and ModuleC
. The following pages should be created:
Documentation/Nightly/Extensions/DoSomethingGreat
Documentation/Nightly/Modules/ModuleA
Documentation/Nightly/Modules/ModuleB
Documentation/Nightly/Modules/ModuleC
In case your extension bundles only one module, the extension name is expected to match the module name. For example, if your extension is named DoSomethingAwesome
, the associated module is expected to be named DoSomethingAwesome
. The following pages will then be created:
Documentation/Nightly/Extensions/DoSomethingAwesome
Documentation/Nightly/Modules/DoSomethingAwesome
where page Extensions/DoSomethingAwesome
redirect to page Modules/DoSomethingAwesome
.
To setup a redirection, simply add the following text to page Extensions/DoSomethingAwesome
:
#REDIRECT [[Documentation/Nightly/Modules/DoSomethingAwesome]]
For an example, see here
More details about redirection are available here: http://www.mediawiki.org/wiki/Help:Redirects
Which URL should be associated with EXTENSION_HOMEPAGE metadata ?
Extensions available through the Slicer Extensions Catalog are expected to have a page created under the Nightly
documentation namespace. The corresponding URL should be associated with the EXTENSION_HOMEPAGE
metadata.
For example:
set(EXTENSION_HOMEPAGE "http://slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/DoSomethingGreat")
set(EXTENSION_HOMEPAGE "http://slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/DoSomethingAwesome")
Note that this also apply for extension bundling only one module. Indeed, in this case the page will redirect to the appropriate module page. For example: http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/SkullStripper
How to rename an extension to add new features ?
If you created an extension to perform Task1, but later on, your module is getting more generic and you add some other tasks, the name of your extension might change. In order to rename, your extension, you should:
- Remove your old extension from the ExtensionsIndex
- Then, submit your extension again (including new features) with a new name
- Make also sure to add redirection from the "deprecated" module documentation to the "new" pages. On the Slicer wiki, this could be using the #REDIRECT instruction.
How to check if an extension is built by Slicer Extensions build system ?
Sometimes an extension could be built either as a standalone package or as a Slicer extension.
To differenciate the two cases, the developer could check for the value of:
<ExtensionName>_BUILD_SLICER_EXTENSION
This variable will be set to ON when the extension is built by the Slicer Extensions build system.
How often extensions are uploaded on the extensions server ?
Slicer extensions are built and uploaded on the extensions server every day.
To be more specific, the frequency of extensions build and upload associated with:
- Slicer nightly package occurs every night and also continuously during the day.
- Slicer 4.10 lastest stable release package occurs every night.
Will an extension be uploaded if associated tests are failing ?
Independently of the extension test results, if the extension could be successfully packaged, it will be uploaded on the extensions server.