Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"
Line 62: | Line 62: | ||
}} | }} | ||
− | ''If you plan to compile Slicer to develop your own extensions and test these extensions on Slicer releases, it is convenient to download the source code directly from SVN and specify the revision number corresponding to the release you want.'' | + | ''If you plan to compile Slicer to develop your own extensions and test these extensions on Slicer releases, it is convenient to download the source code directly from SVN and specify the revision number corresponding to the release you want. To do so, replace <tt><SVNREVISION></tt> in the command below with the selected revision:'' |
<pre> | <pre> | ||
− | svn co http://svn.slicer.org/Slicer4/trunk Slicer- | + | svn co http://svn.slicer.org/Slicer4/trunk Slicer-r<SVNREVISION> -r <SVNREVISION> |
</pre> | </pre> | ||
Line 78: | Line 78: | ||
''More corresponding SVN revision numbers can be found [http://wiki.slicer.org/slicerWiki/index.php/Release_Details here] and [http://slicer.kitware.com/midas3/slicerpackages/view here]'' | ''More corresponding SVN revision numbers can be found [http://wiki.slicer.org/slicerWiki/index.php/Release_Details here] and [http://slicer.kitware.com/midas3/slicerpackages/view here]'' | ||
+ | ''For example, to checkout the source code associated with revision <tt>4.8.1</tt>, you would use the following command:'' | ||
+ | |||
+ | <pre> | ||
+ | svn co http://svn.slicer.org/Slicer4/trunk Slicer-r26813 -r 26813 | ||
+ | </pre> | ||
</ol> | </ol> |
Revision as of 19:53, 20 March 2018
Home < Documentation < Nightly < Developers < Build Instructions < CheckoutSourceCode
For the latest Slicer documentation, visit the read-the-docs. |
CHECKOUT slicer source files
Check out the code using git
and configure the git svn
bridge:
- While it is not enforced, we strongly recommend you to AVOID the use of SPACES for both the
source directory
and thebuild directory
. We mean it.
-
Clone the github repository
cd MyProjects git clone git://github.com/Slicer/Slicer.git
The
Slicer
directory is automatically created after cloning Slicer. -
Setup the development environment:
cd Slicer ./Utilities/SetupForDevelopment.sh
For more details see Development With Git.
On Windows enter the commands above in to a bash shell, such as Git Bash (part of msysgit).
-
Configure the
git svn
bridge to ensure the mapping with svn revision.git-svn is only required for core developers with svn access - other people can skip it.
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
Note for Mac OSX El Capitan:
You might need to link SVN from XCode if you find that git svn
is broken. To get correct links and bypass El Capitan's SIP use these commands
sudo mkdir /Library/Perl/5.18/auto sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi-2level/SVN /Library/Perl/5.18/darwin-thread-multi-2level sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi-2level/auto/SVN /Library/Perl/5.18/auto/
If you plan to compile Slicer to develop your own extensions and test these extensions on Slicer releases, it is convenient to download the source code directly from SVN and specify the revision number corresponding to the release you want. To do so, replace <SVNREVISION> in the command below with the selected revision:
svn co http://svn.slicer.org/Slicer4/trunk Slicer-r<SVNREVISION> -r <SVNREVISION>
Release SVN revision# 4.8.1 26813 4.8.0 26489 4.6.2 25516 4.5.0-1 24735 4.4 23774 4.3.1 22599 4.3.0 22408
More corresponding SVN revision numbers can be found here and here
For example, to checkout the source code associated with revision 4.8.1, you would use the following command:
svn co http://svn.slicer.org/Slicer4/trunk Slicer-r26813 -r 26813