https://www.slicer.org/w/index.php?action=history&feed=atom&title=Documentation%2F4.4%2FDevelopers%2FBuild_Instructions%2FCheckoutSourceCodeDocumentation/4.4/Developers/Build Instructions/CheckoutSourceCode - Revision history2026-06-22T20:38:53ZRevision history for this page on the wikiMediaWiki 1.33.0https://www.slicer.org/w/index.php?title=Documentation/4.4/Developers/Build_Instructions/CheckoutSourceCode&diff=40186&oldid=prevUpdateBot: Nightly -> 4.42014-12-25T06:43:29Z<p>Nightly -> 4.4</p>
<p><b>New page</b></p><div><noinclude>{{documentation/versioncheck}}</noinclude><br />
== CHECKOUT slicer source files ==<br />
<br />
<!--<br />
2. 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]] !.<br />
--><br />
<!--<br />
3. Reading the following page: [[Slicer:git-svn|Slicer guide to <code>git-svn</code>]]<br />
--><br />
<br />
<!--<br />
=== Git ===<br />
--><br />
<span id="Git"></span><br />
<br />
<!--<br />
Checking the code using Git and configuring the <code>git svn</code> bridge is the way to go. If you plan on contributing code, have a look at [[Documentation/{{documentation/version}}/Developers/Tutorials/ContributePatch|How to contribute a patch ?]]<br />
--><br />
<br />
Check out the code using <code>git</code> and configure the <code>git svn</code> bridge:<br />
<br />
<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;"><br />
<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.<br />
</li><br />
</ol><br />
<br />
<ol start="1" style="list-style-type: decimal;"><br />
<br />
<li><br />
<p>Clone the github repository</p><br />
<pre>cd MyProjects<br />
git clone git://github.com/Slicer/Slicer.git</pre><br />
The <code>Slicer</code> directory is automatically created after cloning Slicer.<br />
</li><br />
<br />
<li><br />
<p>Setup the development environment:</p><br />
<pre>cd Slicer<br />
./Utilities/SetupForDevelopment.sh</pre><br />
<p>For more details see [[Documentation/Nightly/Developers/DevelopmentWithGit | Development With Git]].</p><br />
</li><br />
<br />
<li><br />
<p>Configure the <code>git svn</code> bridge to ensure the mapping with svn revision.</p><br />
{{pre2|scroll|<br />
cd Slicer<br />
git svn init http://svn.slicer.org/Slicer4/trunk<br />
git update-ref refs/remotes/git-svn refs/remotes/origin/master<br />
git checkout master<br />
git svn rebase<br />
}}<br />
</li><br />
<br />
<br />
''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.''<br />
<pre><br />
svn co http://svn.slicer.org/Slicer4/trunk Slicer-r23774 -r 23774<br />
</pre><br />
<br />
'''Release''' '''SVN revision#'''<br />
4.4 23774<br />
4.3.1 22599<br />
4.3.0 22408<br />
<br />
''More corresponding SVN revision numbers can be found [http://slicer.kitware.com/midas3/slicerpackages/view here]''<br />
<br />
<br />
</ol><br />
<!--<br />
=== Svn ===<br />
<br />
To simply build Slicer, getting the code using <code>svn</code> is a more straight-forward approach.<br />
<br />
svn co http://svn.slicer.org/Slicer4/trunk Slicer<br />
--></div>UpdateBot