Documentation/Nightly/Developers/FAQ/Modules - Revision history

Moselhy: /* How to modify local version of External module */

2017-08-23T15:37:31Z

How to modify local version of External module

2017-08-23T15:37:17Z

Within a Slicer build-tree, where are located Slicer modules ?

2015-11-26T22:38:21Z

How to call a CLI module from command-line?

2015-11-26T22:22:48Z

How to call a CLI module from command-line?

2015-11-26T22:21:54Z

How to call a CLI module from a C++ loadable module ?

2014-06-24T00:37:08Z

2013-07-02T21:58:30Z

Developer FAQ: {{{1}}}

2013-06-14T07:50:46Z

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

2013-06-12T14:34:53Z

How to build module outside of Slicer source tree

2013-03-04T22:34:35Z

Within a Slicer build-tree, where are located Slicer modules ?

@@ Line 12: / Line 12: @@
 Follow [[Documentation/{{documentation/version}}/Developers/Build_Module|developers guide for building modules]]
-== How to modify local version of External module ==
+== How to modify local version of external module ==
 Some Slicer modules (such as OpenIGTLink and OpenIGTLinkIF) are built as External git projects by CMake scripts in the Slicer/SuperBuild directory.

@@ Line 5: / Line 5: @@
 </includeonly>
-== Within a Slicer build-tree, where are located Slicer modules ? ==
+== Within a Slicer build-tree, where are Slicer modules located? ==
 Slicer module executables and libraries are located in your main Slicer build directory <code>Slicer-Superbuild/Slicer-build</code>. Refer to [[Documentation/{{documentation/version}}/Developers/DirectoryStructure|Directory Structure]] description for more details.

← Older revision		Revision as of 22:38, 26 November 2015
Line 41:		Line 41:
	Slicer.exe --launch CastScalarVolume input.mha output.mha		Slicer.exe --launch CastScalarVolume input.mha output.mha

−	~~Note~~: ~~on Windows, the full~~ name of the Slicer executable is required (''Slicer.exe'', not just ''Slicer'')	+	Notes for windows:
		+	* Full name of the Slicer executable is required (''Slicer.exe'', not just ''Slicer'')
		+	* To get help on command-line arguments the CLI module supports, run:
		+
		+	Slicer.exe --launch CastScalarVolume 2>c:\SomeWriteAbleDirectory\usage.txt

← Older revision		Revision as of 22:22, 26 November 2015
Line 41:		Line 41:
	Slicer.exe --launch CastScalarVolume input.mha output.mha		Slicer.exe --launch CastScalarVolume input.mha output.mha

−	Note: on Windows, the full name of the Slicer executable is required (Slicer.exe)	+	Note: on Windows, the full name of the Slicer executable is required (''Slicer.exe'', not just ''Slicer'')

@@ Line 29: / Line 29: @@
 |}
-== How to call a CLI module from a C++ loadable module ? ==
+== How to call a CLI module from a C++ loadable module? ==
 Discussion: http://slicer-devel.65872.n3.nabble.com/Calling-CLI-module-from-a-C-loadable-module-tt4031930.html
 Example: [https://github.com/Slicer/Slicer/blob/master/Modules/Loadable/CropVolume/Logic/vtkSlicerCropVolumeLogic.cxx#L318-351 vtkSlicerCropVolumeLogic.cxx#L318-351]

← Older revision		Revision as of 00:37, 24 June 2014
Line 28:		Line 28:
	SOURCE_DIR ${CMAKE_BINARY_DIR}/${proj}</pre>		SOURCE_DIR ${CMAKE_BINARY_DIR}/${proj}</pre>
	\|}		\|}
		+
		+	== How to call a CLI module from a C++ loadable module ? ==
		+
		+	Discussion: http://slicer-devel.65872.n3.nabble.com/Calling-CLI-module-from-a-C-loadable-module-tt4031930.html
		+
		+	Example: [https://github.com/Slicer/Slicer/blob/master/Modules/Loadable/CropVolume/Logic/vtkSlicerCropVolumeLogic.cxx#L318-351 vtkSlicerCropVolumeLogic.cxx#L318-351]

← Older revision		Revision as of 21:58, 2 July 2013
Line 11:		Line 11:

	Follow [[Documentation/{{documentation/version}}/Developers/Build_Module\|developers guide for building modules]]		Follow [[Documentation/{{documentation/version}}/Developers/Build_Module\|developers guide for building modules]]
		+
		+	== How to modify local version of External module ==
		+
		+	Some Slicer modules (such as OpenIGTLink and OpenIGTLinkIF) are built as External git projects by CMake scripts in the Slicer/SuperBuild directory.
		+	The SuperBuild process may refresh from the repository unexpectedly, overwriting any local changes. To avoid this, comment out the git settings
		+	in the appropriate external build file while making local edits. For example, in SuperBuild/External_OpenIGTLinkIF.cmake:
		+
		+	{\|
		+	\|<pre>
		+	GIT_REPOSITORY "${git_protocol}://github.com/openigtlink/OpenIGTLinkIF.git"
		+	GIT_TAG "f9b65b1ffd2992862025f3c6ec5fe30e6f5dd395"
		+	SOURCE_DIR ${CMAKE_BINARY_DIR}/${proj}</pre>
		+	\|<pre>
		+	# GIT_REPOSITORY "${git_protocol}://github.com/openigtlink/OpenIGTLinkIF.git"
		+	# GIT_TAG "f9b65b1ffd2992862025f3c6ec5fe30e6f5dd395"
		+	SOURCE_DIR ${CMAKE_BINARY_DIR}/${proj}</pre>
		+	\|}

← Older revision		Revision as of 07:50, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	<noinclude>__TOC__		<noinclude>__TOC__
	={{#titleparts: {{PAGENAME}} \| \| -1 }}=</noinclude><includeonly>		={{#titleparts: {{PAGENAME}} \| \| -1 }}=</noinclude><includeonly>

← Older revision		Revision as of 14:34, 12 June 2013
Line 9:		Line 9:
	== How to build module outside of Slicer source tree ==		== How to build module outside of Slicer source tree ==

−	Follow ~~developers guide for building modules: http://www.slicer.org/slicerWiki/index.php~~/~~Documentation~~/~~Nightly~~/Developers/Build_Module	+	Follow [[Documentation/{{documentation/version}}/Developers/Build_Module\|developers guide for building modules]]