Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"
From Slicer Wiki
| Line 12: | Line 12: | ||
=== Contributor: Git === | === Contributor: Git === | ||
| − | If you plan on contributing code, checking the code using Git and configuring the <code>git-svn</code> bridge is | + | If you plan on contributing code, checking the code using Git and configuring the <code>git-svn</code> bridge is the way to go. See [[Documentation/{{documentation/version}}/Developers/Tutorials/ContributePatch|How to contribute a patch ?]] |
* Clone the github repository | * Clone the github repository | ||
| Line 25: | Line 25: | ||
git checkout master | git checkout master | ||
git svn rebase | git svn rebase | ||
| − | |||
=== Dashboard / Simple build: Svn === | === Dashboard / Simple build: Svn === | ||
Revision as of 05:10, 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
Contributor: Git
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-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
Dashboard / Simple build: Svn
To simply build Slicer, getting the code using svn is a more straight-forward approach.
svn co http://svn.slicer.org/Slicer4/trunk Slicer
