For the latest Slicer developers documentation, visit the Nightly page.
CONFIGURE and generate Slicer solution files
You can configure and generate Slicer solution files using either
- Configure using default options.
- Set the build directory. For example:
- If you downloaded the Qt binary then
qmakewill 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
QT_QMAKE_EXECUTABLEshould be set to the path of the qmake.exe file, which is inside the bin directory (for example,
- Windows doesn't support path longer than 260 characters, please make sure that the total path name of your
Slicer-builddirectory is no longer than 50 characters ( for example
c:\work\Slicer\Slicer-Superbuild(32 characters) is fine)
- Configure using the following commands. By default CMAKE_BUILD_TYPE is set to Debug.
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
where you replace /path/to with the real path on your machine where QtSDK-1.2 is located
- Using top-level directory name like
- Once the project is configured with cmake, generate it
Two projects are generated by either
One of them is in the top-level bin directory
Slicer4-Superbuild and the other one is in the subdirectory
- The first project in
Slicer4-Superbuildmanages 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
Slicer4-Superbuild, which will update and build the external libraries and if successful will then build the subproject Slicer-build.
- The second project in
Slicer4-Superbuild/Slicer-buildis 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
Slicer4-Superbuild/Slicer-buildis necessary (the external libraries are considered built and up to date).
- Warning: An significant 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
Slicer_USE_GIT_PROTOCOL. 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
-DCMAKE_DISABLE_FIND_PACKAGE_Java:BOOL=TRUEwhen configuring Slicer.
- Same applies for OpenSSL:
CMAKE_DISABLE_FIND_PACKAGE_OpenSSL:BOOL=TRUEcan be passed when building Slicer for packaging.