Documentation/4.1/Developers/Build Module - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:22:22Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

JChris.FillionR at 05:43, 21 June 2012

2012-06-21T05:43:30Z

JChris.FillionR at 05:40, 21 June 2012

2012-06-21T05:40:34Z

JChris.FillionR at 09:06, 20 June 2012

2012-06-20T09:06:37Z

JChris.FillionR at 09:02, 20 June 2012

2012-06-20T09:02:17Z

JChris.FillionR: Created page with 'The different type of modules supported by Slicer can easily be build outside of the Slicer source tree. The follo…'

2012-06-20T09:00:12Z

Created page with 'The different [[Documentation/{{documentation/version}}/Developers/Modules|type of modules]] supported by Slicer can easily be build outside of the Slicer source tree. The follo…'

New page

The different [[Documentation/{{documentation/version}}/Developers/Modules|type of modules]] supported by Slicer can easily be build outside of the Slicer source tree.

The following examples are specific to unix-like platforms and can easily be adapted for Windows.

Externally building modules could be achieved doing:
<pre>
$ cd MyModule-build
$ cmake -DSlicer_DIR:PATH=/path/to/Slicer-Superbuild/Slicer-build .
$ make
</pre>

For this to work, in addition to invoke <code>cmake_minimum_required</code> at the top of the CMakeLists.txt, it's important to make sure the following line are added after setting <code>MODULE_NAME</code>:
<pre>
#-----------------------------------------------------------------------------
if(NOT Slicer_SOURCE_DIR)
find_package(Slicer REQUIRED)
include(${Slicer_USE_FILE})
endif()
</pre>

For example:
<pre>
cmake_minimum_required(VERSION 2.8.7)

#-----------------------------------------------------------------------------
set(MODULE_NAME MyModule)
set(MODULE_TITLE ${MODULE_NAME})

string(TOUPPER ${MODULE_NAME} MODULE_NAME_UPPER)

#-----------------------------------------------------------------------------
if(NOT Slicer_SOURCE_DIR)
find_package(Slicer REQUIRED)
include(${Slicer_USE_FILE})
endif()

#-----------------------------------------------------------------------------
add_subdirectory(Logic)

#-----------------------------------------------------------------------------
set(MODULE_EXPORT_DIRECTIVE "Q_SLICER_QTMODULES_${MODULE_NAME_UPPER}_EXPORT")

[...]
</pre>

← Older revision		Revision as of 07:22, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	The different [[Documentation/{{documentation/version}}/Developers/Modules\|type of modules]] supported by Slicer can easily be built outside of the Slicer source tree.		The different [[Documentation/{{documentation/version}}/Developers/Modules\|type of modules]] supported by Slicer can easily be built outside of the Slicer source tree.

@@ Line 28: / Line 28: @@
 <pre>
-cmake_minimum_required(VERSION 2.8.7)  <- - - - ADD THIS
+cmake_minimum_required(VERSION 2.8.8)  <- - - - ADD THIS
 #-----------------------------------------------------------------------------

← Older revision		Revision as of 05:40, 21 June 2012
Line 1:		Line 1:
−	The different [[Documentation/{{documentation/version}}/Developers/Modules\|type of modules]] supported by Slicer can easily be ~~build~~ outside of the Slicer source tree.	+	The different [[Documentation/{{documentation/version}}/Developers/Modules\|type of modules]] supported by Slicer can easily be built outside of the Slicer source tree.

	The following examples are specific to unix-like platforms and can easily be adapted for Windows.		The following examples are specific to unix-like platforms and can easily be adapted for Windows.

@@ Line 2: / Line 2: @@
 The following examples are specific to unix-like platforms and can easily be adapted for Windows.
 Assuming the source code of your module is located in folder <code>MyModule</code>, externally building modules could be achieved doing:
@@ Line 10: / Line 12: @@
 $ make
 </pre>
 For this to work, in addition to invoke <code>cmake_minimum_required</code> at the top of the top-level <code>CMakeLists.txt</code>, it's important to make sure the following line are added after setting <code>MODULE_NAME</code>:
@@ Line 19: / Line 23: @@
 endif()
 </pre>
 For example:
 <pre>
-cmake_minimum_required(VERSION 2.8.7)
+cmake_minimum_required(VERSION 2.8.7)  <- - - - ADD THIS
 #-----------------------------------------------------------------------------
@@ Line 31: / Line 37: @@
 #-----------------------------------------------------------------------------
-if(NOT Slicer_SOURCE_DIR)
+if(NOT Slicer_SOURCE_DIR)  <- - - - - - - - - - ADD THIS
-   find_package(Slicer REQUIRED)
+   find_package(Slicer REQUIRED)  <- - - - - - - ADD THIS
-   include(${Slicer_USE_FILE})
+   include(${Slicer_USE_FILE})  <- - - - - - - - ADD THIS
 endif()

@@ Line 3: / Line 3: @@
 The following examples are specific to unix-like platforms and can easily be adapted for Windows.
-Externally building modules could be achieved doing:
+Assuming the source code of your module is located in folder <code>MyModule</code>, externally building modules could be achieved doing:
 <pre>
 $ cd MyModule-build
-$ cmake -DSlicer_DIR:PATH=/path/to/Slicer-Superbuild/Slicer-build .
+$ cmake -DSlicer_DIR:PATH=/path/to/Slicer-Superbuild/Slicer-build ../MyModule
 $ make
 </pre>
-For this to work, in addition to invoke <code>cmake_minimum_required</code> at the top of the CMakeLists.txt, it's important to make sure the following line are added after setting <code>MODULE_NAME</code>:
+For this to work, in addition to invoke <code>cmake_minimum_required</code> at the top of the top-level <code>CMakeLists.txt</code>, it's important to make sure the following line are added after setting <code>MODULE_NAME</code>:
 <pre>
 #-----------------------------------------------------------------------------