Difference between revisions of "2012 Summer Project Week Breakout Session:SlicerExtensions"

From NAMIC Wiki
Jump to: navigation, search
m
m
Line 44: Line 44:
 
</pre>
 
</pre>
  
−
* 5. Read "How to obtain an API key"
+
* 5. Read [https://github.com/Slicer/ExtensionsIndex#setting-up-an-account-and-obtaining-an-api-key "How to obtain an API key"]
  
 
* 6. Re-configure passing <code>MIDAS_PACKAGE_EMAIL</code> and <code>MIDAS_PACKAGE_API_KEY</code>
 
* 6. Re-configure passing <code>MIDAS_PACKAGE_EMAIL</code> and <code>MIDAS_PACKAGE_API_KEY</code>

Revision as of 19:16, 18 June 2012

Home < 2012 Summer Project Week Breakout Session:SlicerExtensions

Back to agenda

An extension could be seen as a delivery package bundling together one or more Slicer modules. After installing an extension, the associated modules will be presented to the user as built-in ones




Step-by-step: Extension bundling one CLI module

Prerequisites

  • Up-to-date Slicer build - This step by step tutorial has been done using Slicer r20398

Step-by-step

  • 1. Create base structure using ModuleWizard
./Utilities/Scripts/ModuleWizard.py --template ./Extensions/Testing/CLIExtensionTemplate --target ../MyFooExtension MyFooExtension
  • 2. Check that file have been created
cd ..
cd MyFooExtension/
ls
cd ..
cd MyFooExtension-build
  • 3. Configure
cmake -DSlicer_DIR:PATH=/home/jchris/Projects/Slicer4-Superbuild-Debug/Slicer-build/ ../MyFooExtension
  • 4. Build
make -j4
  • 6. Re-configure passing MIDAS_PACKAGE_EMAIL and MIDAS_PACKAGE_API_KEY
cd MyFooExtension-build
cmake -DMIDAS_PACKAGE_EMAIL:STRING=jchris.fillionr@kitware.com -DMIDAS_PACKAGE_API_KEY:STRING=<YOUR_API_KEY> .
  • 7. Publish
make ExperimentalUpload
Retrieved from "https://www.na-mic.org/w/index.php?title=2012_Summer_Project_Week_Breakout_Session:SlicerExtensions&oldid=76428"