Slicer relies on several powerful support libraries. Building slicer has been significantly simplified in slicer 2.4 through the addition of the genlib script.
For anonymous checkout and build on most Linux and Solaris configurations, you only need to follow steps below.
- You will need a recent cvs client; version 1.11.17 is known to work.
- You will need autoconf installed (except on Windows).
- Windows users need to see special download instructions below.
1) get an anonymous checkout
cvs -d :pserver:firstname.lastname@example.org:/projects/cvs/slicer login
and enter 'bwhspl' as the password and then
cvs -d :pserver:email@example.com:/projects/cvs/slicer checkout -r release-2-4-patches slicer2
2) build the required support libraries (Tcl/Tk, GSL, VTK, ITK)
cd slicer2 ./Scripts/genlib.tcl
3) build slicer
These steps will build the entire system for you, and you can use this as the basis for further development such as writing your own custom modules.
Not all the support libraries are easy to build on windows, so you can download a set of precompiled binaries to build against. Insert the following substeps between steps 1) and 2).
1.a) download this file: Slicer2.4-Lib-win32.zip
1.b) unzip the contents into your slicer2 directory. You will end up with the following libraries
Lib/win32/CMake-build Lib/win32/gsl Lib/win32/tcl-build
Then continue with the build steps above.
This assumes you are building with the Microsoft Visual Studio .NET version of the development environment. If you need to use a different compiler, you need to change the GENERATOR variable in the 'slicer_variables.tcl' to 'Visual Studio 7.1'. Note that Slicer has not been fully tested on windows environments other than Microsoft Visual Studio .NET. If CMake complains that "cl" can not compile a simple test program, and you are running Visual Studio 7 .NET 2003, you need to change the GENERATOR variable to "Visual Studio 7 .NET 2003".
If you are using MS VisualStudio 6, you can download the building scripts: Slicer2-MSVC6-InstallScripts.zip. (Note that some modules may not build due to library incompatibilities).
Follow the Generic install steps, but note the extra steps described here: Slicer:Patches_for_the_Mac
These steps are followed as part of the nightly build process for slicer as shown on the slicer dashboard. Compare the builds shown on the dashboard to the system you are trying to build on.