Documentation/4.0/Developers/Build Instructions - Revision history

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

2013-06-14T07:36:11Z

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

Pkarasev: /* Platform Notes */

2013-01-08T04:40:31Z

Platform Notes

Belhachemi at 22:56, 13 May 2012

2012-05-13T22:56:55Z

Lasso at 03:57, 12 May 2012

2012-05-12T03:57:07Z

Belhachemi: /* Quick Build on Debian */

2012-04-07T03:15:41Z

Quick Build on Debian

Belhachemi: /* Platform Notes */

2012-04-06T00:47:58Z

Platform Notes

Belhachemi: /* Unix-like */

2012-04-06T00:45:59Z

Unix-like

JChris.FillionR: /* PREREQUISITES */

2012-04-04T14:08:07Z

PREREQUISITES

JChris.FillionR: /* Using git-svn */

2012-04-04T13:50:20Z

Using git-svn

JChris.FillionR: /* CHECKOUT slicer source files */

2012-04-04T13:49:14Z

CHECKOUT slicer source files

← Older revision		Revision as of 07:36, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	<br>		<br>
	{{mbox		{{mbox

← Older revision		Revision as of 04:40, 8 January 2013
Line 210:		Line 210:

	* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)		* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)
		+	* Unix-Like: remember that "make" wrapping calls to pull source makes it very much not idempotent; re-running make after a build error may get past the previously encountered error. Kind of like re-compiling LaTeX many times to fix references.
	* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180		* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180

← Older revision		Revision as of 22:56, 13 May 2012
Line 211:		Line 211:
	* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)		* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)
	* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180		* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180
−
−
−	~~==Quick Build on Debian==~~
−	~~sudo aptitude update~~
−	~~sudo aptitude install subversion git gcc g++ make cmake-curses-gui libqt4-dev~~
−	~~svn co http://svn.slicer.org/Slicer4/trunk Slicer4~~
−	~~mkdir Slicer4-SuperBuild-Debug~~
−	~~cd Slicer4-SuperBuild-Debug~~
−	~~cmake ../Slicer4~~
−	~~make -j5~~
−
−	~~# runtime dependency:~~
−	~~sudo aptitude install python-tk~~

@@ Line 160: / Line 160: @@
 === A tool returned an error code from "Performing configure step for ..." ===
-CMake has some problems building complex projects on Windows7. See more details in: http://cmake.org/Bug/view.php?id=12957
+Older CMake versions had some problems building complex projects on Windows7 (see more details in: http://cmake.org/Bug/view.php?id=12957).
+Make sure you use the required CMake version.
 === A tool returned an error code from "Performing download step (git clone) for ..." ===

← Older revision		Revision as of 03:15, 7 April 2012
Line 222:		Line 222:
	cmake ../Slicer4		cmake ../Slicer4
	make -j5		make -j5
		+
		+	# runtime dependency:
		+	sudo aptitude install python-tk

← Older revision		Revision as of 00:47, 6 April 2012
Line 212:		Line 212:
	* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)		* Linux Ubuntu: if you have odd rendering artifacts, try disabling visual effects (System/Appearance/Visual Effects)
	* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180		* Windows: If build was OK, but it Slicer doesn't start (gives the error: [bin/Release/SlicerQT-real.exe] exit abnormally - Report the problem.) then one possible root cause is that you have a copy of Python26.dll in your windows system directory (e.g., c:\Windows\System32\python26.dll). The solution is to rename or remove the python dll in the system directory. See more details here: http://www.na-mic.org/Bug/view.php?id=1180
		+
		+
		+	==Quick Build on Debian==
		+	sudo aptitude update
		+	sudo aptitude install subversion git gcc g++ make cmake-curses-gui libqt4-dev
		+	svn co http://svn.slicer.org/Slicer4/trunk Slicer4
		+	mkdir Slicer4-SuperBuild-Debug
		+	cd Slicer4-SuperBuild-Debug
		+	cmake ../Slicer4
		+	make -j5

@@ Line 61: / Line 61: @@
 <pre>
 mkdir Slicer4-SuperBuild-Debug
-cd Slicer4-SuperBuild
+cd Slicer4-SuperBuild-Debug
 ccmake -DQT_QMAKE_EXECUTABLE:FILEPATH=/path/to/QtSDK-1.2/Desktop/Qt/474/gcc/bin/qmake ../Slicer4
 </pre>

@@ Line 7: / Line 7: @@
 == PREREQUISITES ==
 <br>
-<center>To avoid <br>[[#Common_errors|'''Common errors''']], <br>we<br> '''STRONGLY'''<br> recommend to read the<br> <font size="+1">[[Documentation/{{documentation/version}}/Developers/Build Instructions/Prerequisites|Prerequisites]]</font><br> section.</center>
+<center>To avoid <br>[[#Common_errors|'''Common errors''']], <br>we<br> '''STRONGLY'''<br> recommend to read the<br> <font size="+2">[[Documentation/{{documentation/version}}/Developers/Build Instructions/Prerequisites|Prerequisites]]</font><br> section.</center>
 <br><br><br><br>

@@ Line 33: / Line 33: @@
    git svn init http://svn.slicer.org/Slicer4/trunk
    git update-ref refs/remotes/git-svn refs/remotes/origin/master
    git svn rebase

@@ Line 13: / Line 13: @@
 == CHECKOUT slicer source files ==
-You have two options: <code>svn</code> or <code>git-svn</code>
+Two options:  <code>svn</code>   or    <code>git-svn</code>
-To make review and integration of your welcome contributions, we recommends the use of <code>git-svn</code>
+To make '''review''' and '''integration''' of your welcome contributions, we recommends the use of <code>git-svn</code>
 {{ambox
 | type  = warning
 | text  = While it is not enforced, we strongly recommend you to '''AVOID''' the use of '''SPACES''' for both the <code>source directory</code> and the <code>build directory</code>. We mean it.
 }}
-=== Using <code>svn</code> ===
+Note that even if you use <code>svn</code> to check out Slicer source code, you will need to have <code>git</code> installed to checkout and build other libraries. '''YES''', you need to install the things listed in the [[Documentation/{{documentation/version}}/Developers/Build Instructions/Prerequisites|prerequisites]] !.
 === Using <code>git-svn</code> ===
@@ Line 39: / Line 36: @@
 Consider reading the following page: [[Slicer:git-svn|Slicer guide to <code>git-svn</code>]]
 <br><br><br><br>