Difference between revisions of "Documentation/4.1/Developers/Build Instructions/CheckoutSourceCode"
From Slicer Wiki
(Created page with '== CHECKOUT slicer source files == Two options: <code>svn</code> or <code>git-svn</code> To make '''review''' and '''integration''' of your welcome contributions, we reco…') |
(Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | <noinclude>{{documentation/versioncheck}}</noinclude> | ||
== CHECKOUT slicer source files == | == CHECKOUT slicer source files == | ||
Latest revision as of 07:30, 14 June 2013
Home < Documentation < 4.1 < Developers < Build Instructions < CheckoutSourceCode
|
For the latest Slicer documentation, visit the read-the-docs. |
CHECKOUT slicer source files
Two options: svn or git-svn
To make review and integration of your welcome contributions, we recommends the use of git-svn
 |
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. |
Note that 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 !.
Using git-svn
git clone git://github.com/Slicer/Slicer.git 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
Consider reading the following page: Slicer guide to git-svn
Using svn
cd MyProjects svn co http://svn.slicer.org/Slicer4/trunk Slicer
Note: be sure to name your source directory 'Slicer' for compatibility with the build process.
