Slicer3:Build Instructions - Revision history

Grundlett: Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

2019-11-27T02:29:08Z

Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

Pieper: /* getbuildtest on linux */

2012-07-05T14:42:11Z

getbuildtest on linux

Marianna at 18:33, 21 December 2011

2011-12-21T18:33:17Z

Pieper: /* getbuildtest on linux */

2011-12-21T14:20:37Z

getbuildtest on linux

Pieper: /* getbuildtest on linux */

2011-12-19T21:41:50Z

getbuildtest on linux

Pieper: /* getbuildtest on Apple Mac OS X */

2011-12-19T21:40:40Z

getbuildtest on Apple Mac OS X

Pieper: /* getbuildtest on Windows */

2011-08-12T23:05:57Z

getbuildtest on Windows

Pieper: /* getbuildtest on linux */

2011-08-12T22:57:58Z

getbuildtest on linux

Pieper: /* getbuildtest on Windows */

2011-08-12T22:24:21Z

getbuildtest on Windows

Pieper: /* Building the 3.6 release */

2011-08-12T21:10:19Z

Building the 3.6 release

@@ Line 134: / Line 134: @@
 * For information on using the launcher to debug with gdb, see: [http://www.na-mic.org/Wiki/index.php/Slicer3_Q&A_2008-11-18#Debugging]
 * For debugging with Visual Studio, see: [http://www.na-mic.org/Wiki/index.php/User:Pieper#Launching_visual_studio_for_slicer3_debugging]
-* For debugging command line modules, see [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Debugging]
+* For debugging command line modules, see [[Slicer3:Execution_Model_Documentation:Debugging]
-Note you can also debug in XCode with similar methods, but you may need to manually copy the DYLD_LIBRARY_PATH into the project properties (XCode does not seem to inherit from its parent shell).
+Note|you can also debug in XCode with similar methods, but you may need to manually copy the DYLD_LIBRARY_PATH into the project properties (XCode does not seem to inherit from its parent shell).
 == Updating Your getbuildtest Build ==
@@ Line 183: / Line 183: @@
   yum install subversion cvs gcc-c++ libX11-devel libXt-devel make
-You also need git for Centos but it isn't in the standard yum install.  One option is to install it using the instructions [http://www.webtatic.com/news/2011/05/latest-updates-git-1-7-5-1-httpd-itk-2-2-18/ here].
+You also need git for Centos but it isn't in the standard yum install.  One option is to install it using the instructions [http://www.webtatic.com/news/2011/05/latest-updates-git-1-7-5-1-httpd-itk-2-2-18/ here]].
 Fedora 13 required packages as reported by John Drozd:

← Older revision		Revision as of 14:42, 5 July 2012
Line 174:		Line 174:

	sudo apt-get install libosmesa6-dev		sudo apt-get install libosmesa6-dev
		+
		+	For Ubuntu 12.04 you also need to install:
		+
		+	sudo apt-get install make
		+

	CentOS 5.5 (Red Hat) one line install:		CentOS 5.5 (Red Hat) one line install:

@@ Line 2: / Line 2: @@
 To compile and build Slicer3, you need a set of development packages installed on your machine:
-* [[Slicer3:Build_Instructions#getbuildtest_on_linux| pre-requisite material for Linux]]
-* [[Slicer3:Build_Instructions#getbuildtest_on_Windows| pre-requisite material for Windows]]
+Pre-requisite material:
-* [[Slicer3:Build_Instructions#getbuildtest_on_Apple_Mac_OS_X |pre-requisite material for Mac]]
+* [[Slicer3:Build_Instructions#getbuildtest_on_linux| Linux]]
 There's a script called getbuildtest.tcl that makes the support libraries (VTK, ITK, teem, etc) and also builds slicer and does a dashboard submission.  (Click [[Slicer3:getbuildtest | here for background on getbuildtest]] and the experimental getbuildtest2 version).
 = Building the 3.6 release =
 For Linux and Mac, just do the following two commands. If you are a Windows user, you need to [[Slicer3:Build_Instructions_Windows#Open_cygwin_terminal_window | open a cygwin terminal window]] and type the commands in that window.

← Older revision		Revision as of 14:20, 21 December 2011
Line 164:		Line 164:
	* opengl/mesa (libgl1-mesa-dev on Ubuntu)		* opengl/mesa (libgl1-mesa-dev on Ubuntu)
	* glu (libglu1-mesa-dev on Ubuntu)		* glu (libglu1-mesa-dev on Ubuntu)
		+	* tcl

@@ Line 197: / Line 197: @@
 *Turning off python support in the build settings (USE_PYTHON set to "OFF")
 *Set the USE_SYSTEM_PYTHON to "true"
 == getbuildtest on Windows ==

← Older revision		Revision as of 21:40, 19 December 2011
Line 243:		Line 243:

	Set the flag VTK_USE_RPATH=ON (see the post [http://vtk.1045678.n5.nabble.com/Compile-error-on-OS-X-10-5-td1245851.html here])		Set the flag VTK_USE_RPATH=ON (see the post [http://vtk.1045678.n5.nabble.com/Compile-error-on-OS-X-10-5-td1245851.html here])
		+
		+	For the latest version of Mac OS X (10.7) the correct X11 comes pre-installed.
		+
		+	As of December 2011, only Slicer3 trunk compiles on 10.7 (not the Slicer-3-6 branch). Also python is not correctly compiled on 10.7 so it should be disabled by editing the Slicer3_USE_PYTHON option in slicer_variables.tcl

	== getbuildtest on Solaris ==		== getbuildtest on Solaris ==

@@ Line 222: / Line 222: @@
 * Be sure your visual studio version is fully patched (or random crashes may occur).
 * Slicer3 is tested on the English language version of windows.  Other languages may cause lead to mysterious build errors.  For example, Chinese language for non-Unicode programs (system locale) in Window 7 is known to have problems with KWWidgets.
-* Be sure your environment variables for TEMP and TMP are ''writable by your user account''.  If the temp variables point, for example, to c:/windows/TEMP then non-administrator account cannot write to it and some build steps will fail.  The correct temp paths appear to be: %USERPROFILE%\AppData\Local\Temp for windows 7.
+* Be sure your environment variables for TEMP and TMP are ''writable by your user account''.  If the temp variables point, for example, to c:/windows/TEMP then non-administrator account cannot write to it and some build steps will fail.  The correct temp paths appear to be: %USERPROFILE%\AppData\Local\Temp for windows 7.  Another option is to launch your cygwin shell using the Run As Administrator option.
 Follow this link for [[Slicer3:Build_Instructions_Windows#Troubleshooting | common errors and troubleshooting on windows]].

@@ Line 19: / Line 19: @@
 For Slicer 3.4 build instructions, please see
 [http://www.slicer.org/slicerWiki/index.php?title=Slicer3:Build_Instructions&oldid=14059#Building_the_3.4_release|a previous version of this page].
 = Building the latest development version =