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

JChris.FillionR at 06:00, 5 May 2020

2020-05-05T06:00:27Z

JChris.FillionR: /* What is the ITKFactoryRegistration library ? */

2019-05-01T16:50:42Z

What is the ITKFactoryRegistration library ?

JChris.FillionR: /* What is the ITKFactoryRegistration library ? */

2019-05-01T16:50:22Z

What is the ITKFactoryRegistration library ?

JChris.FillionR: /* What is the ITKFactoryRegistration library ? */

2019-05-01T16:46:41Z

What is the ITKFactoryRegistration library ?

JChris.FillionR: /* What is the ITKFactoryRegistration library ? */

2019-05-01T16:44:24Z

What is the ITKFactoryRegistration library ?

JChris.FillionR: /* What is ITKFactoryRegistration library ? */

2019-05-01T16:44:00Z

What is ITKFactoryRegistration library ?

JChris.FillionR: /* Developer FAQ: {{{1}}} */

2019-05-01T16:43:49Z

Developer FAQ: {{{1}}}

JChris.FillionR at 17:24, 6 July 2016

2016-07-06T17:24:06Z

JChris.FillionR: /* Developer FAQ: {{{1}}} */

2016-07-06T17:23:16Z

Developer FAQ: {{{1}}}

JChris.FillionR: /* Developer FAQ: {{{1}}} */

2014-09-27T02:15:34Z

Developer FAQ: {{{1}}}

← Older revision		Revision as of 06:00, 5 May 2020
Line 120:		Line 120:
	Notes:		Notes:
	* Since calling <tt>include(${Slicer_USE_FILE})</tt> already set <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> in the current scope, explicitly setting the variable afterward is not required.		* Since calling <tt>include(${Slicer_USE_FILE})</tt> already set <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> in the current scope, explicitly setting the variable afterward is not required.
		+
		+	== How to configure network proxy ? ==
		+
		+	As explained [http://cmake.3232098.n2.nabble.com/set-proxy-with-cmake-file-download-td4715827.html#a4752250 here], proxy configured by setting <tt>http_proxy</tt> and <tt>https_proxy</tt> environment variables will automatically be used by CMake.

← Older revision		Revision as of 16:50, 1 May 2019
Line 119:		Line 119:

	Notes:		Notes:
−	* Since calling <tt>include(${Slicer_USE_FILE})</tt> ~~ensures that~~ <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> ~~is already set~~, explicitly setting the variable afterward is not required.	+	* Since calling <tt>include(${Slicer_USE_FILE})</tt> already set <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> in the current scope, explicitly setting the variable afterward is not required.

← Older revision		Revision as of 16:50, 1 May 2019
Line 117:		Line 117:

	The introduction of a shared library named <tt>ITKFactoryRegistration</tt> (see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21592 r21592]) that should be linked against to ensure loading of the factories is performed once. This approach requires user of ITK libraries to explicitly set the ITK variable <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> to <tt>1</tt> before calling <tt>include(${ITK_USE_FILE})</tt>.		The introduction of a shared library named <tt>ITKFactoryRegistration</tt> (see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21592 r21592]) that should be linked against to ensure loading of the factories is performed once. This approach requires user of ITK libraries to explicitly set the ITK variable <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> to <tt>1</tt> before calling <tt>include(${ITK_USE_FILE})</tt>.
		+
		+	Notes:
		+	* Since calling <tt>include(${Slicer_USE_FILE})</tt> ensures that <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> is already set, explicitly setting the variable afterward is not required.

@@ Line 112: / Line 112: @@
 == What is the ITKFactoryRegistration library ? ==
-The <tt>ITKFactoryRegistration</tt> library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded.
+The <tt>ITKFactoryRegistration</tt> library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded. See [https://issues.slicer.org/view.php?id=2813 Slicer issue #2813]
 Indeed, when ITKv4 is build shared, the library holding the factory registration code are build statically. As a consequence, when CLI modules are loaded as library the factory are registered multiple times. More than 800 factories were registered and this was leading to poor performance when loading images.
 The introduction of a shared library named <tt>ITKFactoryRegistration</tt> (see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21592 r21592]) that should be linked against to ensure loading of the factories is performed once. This approach requires user of ITK libraries to explicitly set the ITK variable <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> to <tt>1</tt> before calling <tt>include(${ITK_USE_FILE})</tt>.

@@ Line 112: / Line 112: @@
 == What is the ITKFactoryRegistration library ? ==
-This library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded.
+The <tt>ITKFactoryRegistration</tt> library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded.
 Indeed, when ITKv4 is build shared, the library holding the factory registration code are build statically. As a consequence, when CLI modules are loaded as library the factory are registered multiple times. More than 800 factories were registered and this was leading to poor performance when loading images.
 The introduction of a shared library named <tt>ITKFactoryRegistration</tt> (see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21592 r21592]) that should be linked against to ensure loading of the factories is performed once. This approach requires user of ITK libraries to explicitly set the ITK variable <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> to <tt>1</tt> before calling <tt>include(${ITK_USE_FILE})</tt>.

@@ Line 110: / Line 110: @@
 * CMake issue [http://public.kitware.com/Bug/view.php?id=14156 #14156]
-== What is ITKFactoryRegistration library ? ==
+== What is the ITKFactoryRegistration library ? ==
 This library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded.

← Older revision		Revision as of 16:43, 1 May 2019
Line 109:		Line 109:
	* Slicer issue [http://na-mic.org/Mantis/view.php?id=3116#c8649 #3116]		* Slicer issue [http://na-mic.org/Mantis/view.php?id=3116#c8649 #3116]
	* CMake issue [http://public.kitware.com/Bug/view.php?id=14156 #14156]		* CMake issue [http://public.kitware.com/Bug/view.php?id=14156 #14156]
		+
		+	== What is ITKFactoryRegistration library ? ==
		+
		+	This library ensures that no duplicated ITK IO factories are registered when CLI shared library modules are loaded.
		+
		+	Indeed, when ITKv4 is build shared, the library holding the factory registration code are build statically. As a consequence, when CLI modules are loaded as library the factory are registered multiple times. More than 800 factories were registered and this was leading to poor performance when loading images.
		+
		+	The introduction of a shared library named <tt>ITKFactoryRegistration</tt> (see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21592 r21592]) that should be linked against to ensure loading of the factories is performed once. This approach requires user of ITK libraries to explicitly set the ITK variable <tt>ITK_NO_IO_FACTORY_REGISTER_MANAGER</tt> to <tt>1</tt> before calling <tt>include(${ITK_USE_FILE})</tt>.

← Older revision		Revision as of 17:24, 6 July 2016
Line 102:		Line 102:

	See Slicer issue [http://www.na-mic.org/Bug/view.php?id=3325 #3325]		See Slicer issue [http://www.na-mic.org/Bug/view.php?id=3325 #3325]
		+
		+	== Why distributed CMake can not be used on Ubuntu 12.04 and above ? ==
		+
		+	* http://slicer-devel.65872.n3.nabble.com/PYTHON-INCLUDE-DIR2-when-building-Slicer4-td4028557.html
		+	* Slicer issue [http://na-mic.org/Mantis/view.php?id=3103 #3103]
		+	* Slicer issue [http://na-mic.org/Mantis/view.php?id=3116#c8649 #3116]
		+	* CMake issue [http://public.kitware.com/Bug/view.php?id=14156 #14156]

← Older revision		Revision as of 17:23, 6 July 2016
Line 98:		Line 98:

	To build Slicer with SSL support, you need to build (or download) Qt with SSL support and configure Slicer with <code>-DSlicer_USE_PYTHONQT_WITH_OPENSSL:BOOL=ON</code>		To build Slicer with SSL support, you need to build (or download) Qt with SSL support and configure Slicer with <code>-DSlicer_USE_PYTHONQT_WITH_OPENSSL:BOOL=ON</code>
		+
		+	== Why Qt 4 >= 4.8.5 should be used on Ubuntu 12.04 and above ? ==
		+
		+	See Slicer issue [http://www.na-mic.org/Bug/view.php?id=3325 #3325]

← Older revision		Revision as of 02:15, 27 September 2014
Line 15:		Line 15:

	See [[Documentation/{{documentation/version}}/Developers/DirectoryStructure\|Slicer directory structure]]		See [[Documentation/{{documentation/version}}/Developers/DirectoryStructure\|Slicer directory structure]]
		+
		+	== What is a clean build ? ==
		+
		+	Doing a ''clean build'' means that
		+
		+	(1) all directories and files in the top-level build directory <code>~/Projects/Slicer-SuperBuild</code> are removed.
		+
		+	and
		+
		+	(2) you updated your source checkout and have no locally modified files.

	== What to do if QtSDK installer hangs ? ==		== What to do if QtSDK installer hangs ? ==