CHECKOUT slicer source files
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.
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
- Setup the development environment using the
SetupForDevelopment.shscript as described on our Development With Git page.
- 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