Difference between revisions of "Slicer3:Module Building"
From NAMIC Wiki
TerryLorber (talk | contribs) |
TerryLorber (talk | contribs) |
||
Line 9: | Line 9: | ||
Dependency: Other | Dependency: Other | ||
Dependency: Another | Dependency: Another | ||
+ | |||
+ | Only the "Name:" entry is required. | ||
=== CMakeLists.txt === | === CMakeLists.txt === |
Revision as of 15:40, 29 April 2008
Home < Slicer3:Module BuildingIn order to create a Slicer3 interactice GUI module that can be discovered at run-time, the following two files need to be created or modified.
ExampleModule.txt
Create this file alongside vtkExampleModuleGUI and vtkExampleModuleLogic. It's contents are key:value pairs describing the module. It's also used to configure build-time module selection. For loadable module support the following entries are used:
Name: Example GUIName: ExMod Dependency: Other Dependency: Another
Only the "Name:" entry is required.
CMakeLists.txt
In order to create the necessary source files to enable an module to be discovered at run-time, use the GENERATELM macro in the module's CMakeLists.txt file:
GENERATELM(ExampleModule_SRCS ExampleModule.txt)
This macro must be included after any TCL wrapping macros, as it adds to the source files for the library.