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

From Slicer Wiki
Jump to: navigation, search
Line 17: Line 17:
   git clone git://github.com/Slicer/Slicer.git
   git clone git://github.com/Slicer/Slicer.git
* Setup the development environment using the [https://github.com/Slicer/Slicer/blob/master/Utilities/SetupForDevelopment.sh <code>SetupForDevelopment.sh</code>] script as described on our [[Documentation/Nightly/Developers/DevelopmentWithGit | Development With Git]] page.
* Configure the <code>git-svn</code> bridge to ensure the mapping with svn revision.
* Configure the <code>git-svn</code> bridge to ensure the mapping with svn revision.

Revision as of 14:26, 14 April 2013

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

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 !.

3. Reading the following page: Slicer guide to git-svn


If you plan on contributing code, checking the code using Git and configuring the git-svn bridge is the way to go. See 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