|
|
Line 1: |
Line 1: |
− | In 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.
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:Module_Building here]</font></big> |
− | | |
− | === 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.
| |
Revision as of 15:02, 22 May 2008
Home < Slicer3:Module BuildingNote: We are migrating this content to the slicer.org domain - The newer page is here