Documentation/4.1/Developers/Build Instructions/Configure - Revision history

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

2013-06-14T07:30:09Z

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

JChris.FillionR: /* Windows */

2012-07-09T13:33:01Z

Windows

JChris.FillionR: /* Windows */

2012-07-09T13:31:59Z

Windows

JChris.FillionR: /* Windows */

2012-07-09T13:31:14Z

Windows

Finetjul: /* Unix-like */

2012-07-03T14:34:40Z

Unix-like

JChris.FillionR: moved Template:Documentation/4.1/Developers/Build Instructions/Configure to Documentation/4.1/Developers/Build Instructions/Configure

2012-06-12T04:04:42Z

moved Template:Documentation/4.1/Developers/Build Instructions/Configure to Documentation/4.1/Developers/Build Instructions/Configure

Matt.mccormick: /* General information */

2012-06-05T22:31:30Z

General information

JChris.FillionR: Created page with '== CONFIGURE and generate Slicer solution files == You can configure and generate Slicer solution files using either `ccmake` or `cmake-gui`. === Per-platf…'

2012-06-05T02:10:52Z

Created page with '== CONFIGURE and generate Slicer solution files == You can configure and generate Slicer solution files using either <code>ccmake</code> or <code>cmake-gui</code>. === Per-platf…'

New page

== CONFIGURE and generate Slicer solution files ==
You can configure and generate Slicer solution files using either <code>ccmake</code> or <code>cmake-gui</code>.

=== Per-platform instructions===
==== Windows ====
*'''Recommended''': <code>cmake-gui</code>
** Configure using default options.
* '''Remarks''':
#If you downloaded the Qt binary then <code>qmake</code> will be detected and all paths will be set automatically.
#If you built your own Qt (e.g. in Debug mode for use with the designer) set the <code>QT_QMAKE_EXECUTABLE</code> in <code>cmake-gui</code>.<code>QT_QMAKE_EXECUTABLE</code> should be set to the path of the qmake.exe file, which is inside the bin directory (for example, <code>/path/to/qt-everywhere-opensource-build-4.7.4/bin/qmake.exe</code>).
#Windows doesn't support path longer than 260 characters, please make sure that the total path name of your <code>Slicer-build</code> directory is no longer than 50 characters ( for example <code>c:\work\Slicer\Slicer-Superbuild</code> (32 characters) is fine)

==== Unix-like ====
*'''Recommended''': <code>ccmake</code>
** Configure using the following commands. By default '''CMAKE_BUILD_TYPE''' is set to '''Debug'''.
<pre>
mkdir Slicer4-SuperBuild-Debug
cd Slicer4-SuperBuild-Debug
ccmake -DQT_QMAKE_EXECUTABLE:FILEPATH=/path/to/QtSDK-1.2/Desktop/Qt/474/gcc/bin/qmake ../Slicer
</pre>
* '''Remarks''':
# Using top-level directory name like <code>Slicer-Superbuild-Release</code> or <code>Slicer-Superbuild-Debug</code> is recommended.

=== General information ===

Two projects are generated by either <code>cmake</code>, <code>ccmake</code> or <code>cmake-gui</code>.

One of them is in the top-level bin directory <code>Slicer4-Superbuild</code> and the other one is in the subdirectory <code>Slicer-build</code>:

<pre>Slicer4-Superbuild/Slicer-build</pre>

# The first project in <code>Slicer4-Superbuild</code> manages all the external dependencies of Slicer (VTK, ITK, Python, ...). To build Slicer for the first time, run make (or build the solution file in Visual Studio) in <code>Slicer4-Superbuild</code>, which will update and build the external libraries and if successful will then build the subproject Slicer-build.<br>
# The second project in <code>Slicer4-Superbuild/Slicer-build</code> is the "traditional" build directory of Slicer. After local changes in Slicer (or after an svn update on the source directory of Slicer), only running make (or building the solution file in Visual Studio) in <code>Slicer4-Superbuild/Slicer-build</code> is necessary (the external libraries are considered built and up to date). <br>
#'''Warning''': An important amount of disk space is required to compile Slicer in Debug (>10GB on Windows)

=== Workaround firewall blocking git protocol ===
* Some firewall will be blocking the git protocol, a possible workaround is to configure Slicer disabling the option <code>Slicer_USE_GIT_PROTOCOL</code>. Then http protocol will be used instead. Consider also reading https://github.com/commontk/CTK/issues/33

=== Notes for advanced users ===
* By default, if CMake finds Java on your machine, it automatically builds Java CLIs. If you don't want any Java in your Slicer (or if you don't want to install Java on your Mac Os X), you can pass <code>-DCMAKE_DISABLE_FIND_PACKAGE_Java:BOOL=TRUE</code> when configuring Slicer.
* Same applies for OpenSSL: <code>CMAKE_DISABLE_FIND_PACKAGE_OpenSSL:BOOL=TRUE</code> can be passed when building Slicer for packaging.

← Older revision		Revision as of 07:30, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	== CONFIGURE and generate Slicer solution files ==		== CONFIGURE and generate Slicer solution files ==
	You can configure and generate Slicer solution files using either <code>ccmake</code> or <code>cmake-gui</code>.		You can configure and generate Slicer solution files using either <code>ccmake</code> or <code>cmake-gui</code>.

@@ Line 6: / Line 6: @@
 *'''Recommended''': <code>cmake-gui</code>
 ** Configure using default options.
-** Set the build directory to be either <code>\path\to\Slicer4-SuperBuild-Debug</code> or <code>\path\to\Slicer4-SuperBuild-Release</code>
+** Set the build directory. For example: <code>C:\Slicer4-SuperBuild-Debug</code> or <code>C:\Slicer4-SuperBuild-Release</code>
 * '''Remarks''':
 #If you downloaded the Qt binary then <code>qmake</code> will be detected and all paths will be set automatically.

@@ Line 19: / Line 19: @@
 ccmake -DQT_QMAKE_EXECUTABLE:FILEPATH=/path/to/QtSDK-1.2/Desktop/Qt/474/gcc/bin/qmake ../Slicer
 </pre>
 * '''Remarks''':
 # Using top-level directory name like <code>Slicer-Superbuild-Release</code> or <code>Slicer-Superbuild-Debug</code> is recommended.

← Older revision	Revision as of 04:04, 12 June 2012
(No difference)

@@ Line 32: / Line 32: @@
 # The first project in <code>Slicer4-Superbuild</code> manages all the external dependencies of Slicer (VTK, ITK, Python, ...). To build Slicer for the first time, run make (or build the solution file in Visual Studio) in <code>Slicer4-Superbuild</code>, which will update and build the external libraries and if successful will then build the subproject Slicer-build.<br>
 # The second project in <code>Slicer4-Superbuild/Slicer-build</code> is the "traditional" build directory of Slicer.  After local changes in Slicer (or after an svn update on the source directory of Slicer), only running make (or building the solution file in Visual Studio) in <code>Slicer4-Superbuild/Slicer-build</code> is necessary (the external libraries are considered built and up to date). <br>
-#'''Warning''': An important amount of disk space is required to compile Slicer in Debug (>10GB on Windows)
+#'''Warning''': An significant amount of disk space is required to compile Slicer in Debug (>10GB on Windows)
 === Workaround firewall blocking git protocol ===

Documentation/4.1/Developers/Build Instructions/Configure - Revision history

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

JChris.FillionR: /* Windows */

JChris.FillionR: /* Windows */

JChris.FillionR: /* Windows */

Finetjul: /* Unix-like */

JChris.FillionR: moved Template:Documentation/4.1/Developers/Build Instructions/Configure to Documentation/4.1/Developers/Build Instructions/Configure

Matt.mccormick: /* General information */

JChris.FillionR: Created page with '== CONFIGURE and generate Slicer solution files == You can configure and generate Slicer solution files using either ccmake or cmake-gui. === Per-platf…'

JChris.FillionR: Created page with '== CONFIGURE and generate Slicer solution files == You can configure and generate Slicer solution files using either `ccmake` or `cmake-gui`. === Per-platf…'