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

From Slicer Wiki
Jump to: navigation, search
(Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887)
Line 1: Line 1:
== CHECKOUT slicer source files ==
== CHECKOUT slicer source files ==

Revision as of 07:54, 14 June 2013

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

For the latest Slicer documentation, visit the read-the-docs.

CHECKOUT slicer source files

1. While it is not enforced, we strongly recommend you to AVOID the use of SPACES for both the source directory and the build directory. We mean it.

2. Even if you use svn to check out Slicer source code, you will need to have git installed to checkout and build other libraries. YES, you need to install the things listed in the prerequisites !.


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


To simply build Slicer, getting the code using svn is a more straight-forward approach.

 svn co http://svn.slicer.org/Slicer4/trunk Slicer