Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"
From Slicer Wiki
| Line 11: | Line 11: | ||
=== Checkout source code === | === Checkout source code === | ||
| − | |||
| − | |||
If you plan on contributing code, checking the code using Git and configuring the <code>git-svn</code> bridge is recommended. | If you plan on contributing code, checking the code using Git and configuring the <code>git-svn</code> bridge is recommended. | ||
| Line 28: | Line 26: | ||
git svn rebase | git svn rebase | ||
| − | + | ||
To simply build Slicer, getting the code using <code>svn</code> is a more straight-forward approach. | To simply build Slicer, getting the code using <code>svn</code> is a more straight-forward approach. | ||
svn co http://svn.slicer.org/Slicer4/trunk Slicer | svn co http://svn.slicer.org/Slicer4/trunk Slicer | ||
Revision as of 05:07, 18 February 2013
Home < Documentation < Nightly < Developers < Build Instructions < CheckoutSourceCodeCHECKOUT 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
Checkout source code
If you plan on contributing code, checking the code using Git and configuring the git-svn bridge is recommended.
- Clone the github repository
git clone git://github.com/Slicer/Slicer.git
- Configure the
git-svnbridge 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
