Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"

From Slicer Wiki
Jump to: navigation, search
Line 2: Line 2:
 
== CHECKOUT slicer source files ==
 
== CHECKOUT slicer source files ==
  
 +
<!--
 
<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.
 
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.
 +
-->
 
<!--
 
<!--
 
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]] !.
 
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]] !.

Revision as of 01:41, 15 June 2013

Home < Documentation < Nightly < Developers < Build Instructions < CheckoutSourceCode


CHECKOUT slicer source files


Git

Checking the code using Git and configuring the git svn bridge is the way to go. If you plan on contributing code, have a look at How to contribute a patch ?

  • Clone the github repository
 git clone git://github.com/Slicer/Slicer.git
  • Configure the git svn bridge to ensure the mapping with svn revision.
  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