https://www.slicer.org/w/index.php?action=history&feed=atom&title=Documentation%2F4.3%2FDevelopers%2FBuild_Instructions%2FCheckoutSourceCodeDocumentation/4.3/Developers/Build Instructions/CheckoutSourceCode - Revision history2026-05-06T22:49:08ZRevision history for this page on the wikiMediaWiki 1.33.0https://www.slicer.org/w/index.php?title=Documentation/4.3/Developers/Build_Instructions/CheckoutSourceCode&diff=35163&oldid=prevUpdateBot: Nightly -> 4.32013-09-05T03:31:26Z<p>Nightly -> 4.3</p>
<p><b>New page</b></p><div><noinclude>{{documentation/versioncheck}}</noinclude><br />
== CHECKOUT slicer source files ==<br />
<br />
<!--<br />
<br><br />
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 />
--><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 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 />
</ol><br />
<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