Unknown user: Text replacement - "slicerWiki/index.php" to "wiki"

2019-11-21T17:05:30Z

Text replacement - "slicerWiki/index.php" to "wiki"

UpdateBot: Nightly -> 4.10

2018-10-19T00:41:20Z

Nightly -> 4.10

New page

<noinclude>{{documentation/versioncheck}}</noinclude>
== CHECKOUT slicer source files ==









Check out the code using <code>git</code> and configure the <code>git svn</code> bridge:

<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>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.
</li>
</ol>

<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>Due to maximum path length limitations during build the build process, source and build folders must be located in a folder with very short total path length. This is expecially critical on Windows. For example, C:\D\S4 for source and C:\D\S4R for release-mode build folder works.
</li>
</ol>

<ol start="1" style="list-style-type: decimal;">

<li>
Clone the github repository
<pre>cd MyProjects
git clone git://github.com/Slicer/Slicer.git</pre>
The <code>Slicer</code> directory is automatically created after cloning Slicer.
</li>

<li>
Setup the development environment:
<pre>cd Slicer
./Utilities/SetupForDevelopment.sh</pre>
For more details see [[Documentation/Nightly/Developers/DevelopmentWithGit | Development With Git]].
On Windows enter the commands above in to a bash shell, such as Git Bash (part of msysgit) or use a Git client with a graphical user interface.
</li>

<li>
Configure the <code>git svn</code> bridge to ensure the mapping with svn revision.git-svn is only required for core developers with svn access - other people can skip it.
{{pre2|scroll|
cd Slicer
git svn init http://svn.slicer.org/Slicer4/trunk
git update-ref refs/remotes/git-svn refs/remotes/origin/master
git checkout master
git svn rebase
}}
</li>

Note for Mac OSX El Capitan:

You might need to link SVN from XCode if you find that <code>git svn</code> is broken. To get correct links and bypass El Capitan's SIP use these commands 
{{pre2|scroll|
sudo mkdir /Library/Perl/5.18/auto
sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi-2level/SVN /Library/Perl/5.18/darwin-thread-multi-2level
sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi-2level/auto/SVN /Library/Perl/5.18/auto/
}}

''If you plan to compile Slicer to develop your own extensions and test these extensions on Slicer releases, it is convenient to download the source code directly from SVN and specify the revision number corresponding to the release you want. To do so, replace <tt><MARKER></tt> and <tt><SVNREVISION></tt> in the command below with the selected revision and marker:''
<pre>
svn co http://svn.slicer.org/Slicer4/<MARKER> Slicer-r<SVNREVISION> -r <SVNREVISION>
</pre>

'''Release''' '''SVN revision#''' '''Marker'''
4.8.1 26813 branches/Slicer-4-8
4.8.0 26489 trunk
4.6.2 25516 branches/Slicer-4-6
4.5.0-1 24735 trunk
4.4 23774 trunk
4.3.1 22599 branches/Slicer-4-3
4.3.0 22408 trunk

''More corresponding SVN revision numbers can be found [http://wiki.slicer.org/slicerWiki/index.php/Release_Details here] and [http://slicer.kitware.com/midas3/slicerpackages/view here]''. The <tt><MARKER></tt> can be found at the bottom of this page http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=SVNREVISION by replacing <tt>SVNREVISION</tt> with the selected revision.

''For example, to checkout the source code associated with revision <tt>4.8.1</tt>, you would use the following command:''

<pre>
svn co http://svn.slicer.org/Slicer4/branches/Slicer-4-8 Slicer-r26813 -r 26813
</pre>

</ol>

@@ Line 81: / Line 81: @@
 .3.0               22408               trunk
-''More corresponding SVN revision numbers can be found [http://wiki.slicer.org/slicerWiki/index.php/Release_Details here] and [http://slicer.kitware.com/midas3/slicerpackages/view here]''. The <tt><MARKER></tt> can be found at the bottom of this page http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=SVNREVISION by replacing <tt>SVNREVISION</tt> with the selected revision.
+''More corresponding SVN revision numbers can be found [http://wiki.slicer.org/wiki/Release_Details here] and [http://slicer.kitware.com/midas3/slicerpackages/view here]''. The <tt><MARKER></tt> can be found at the bottom of this page http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=SVNREVISION by replacing <tt>SVNREVISION</tt> with the selected revision.
 ''For example, to checkout the source code associated with revision <tt>4.8.1</tt>, you would use the following command:''

Documentation/4.10/Developers/Build Instructions/CheckoutSourceCode - Revision history

Unknown user: Text replacement - "slicerWiki/index.php" to "wiki"

UpdateBot: Nightly -> 4.10