Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"

From Slicer Wiki
Jump to: navigation, search
Line 64: Line 64:
   4.3.0              22408
   4.3.0              22408
''More corresponding SVN revision numbers can be found [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]''

Revision as of 17:13, 21 January 2015

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:

  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.
  1. Clone the github repository

    cd MyProjects
    git clone git://github.com/Slicer/Slicer.git

    The Slicer directory is automatically created after cloning Slicer.

  2. Setup the development environment:

    cd Slicer

    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).

  3. Configure the git svn bridge 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
  4. 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.
    svn co http://svn.slicer.org/Slicer4/trunk Slicer-r23774 -r 23774
     Release         SVN revision#
     4.4                 23774
     4.3.1               22599
     4.3.0               22408

    More corresponding SVN revision numbers can be found here and here