Difference between revisions of "Documentation/Nightly/Developers/Build Instructions/CheckoutSourceCode"
From Slicer Wiki
Tag: 2017 source edit |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 18: | Line 18: | ||
--> | --> | ||
| − | Check out the code using <code>git</code> and configure the <code>git svn</code> bridge: | + | Check out the code using <code>git</code><!--and configure the <code>git svn</code> bridge-->: |
<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;"> | <ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;"> | ||
| Line 26: | Line 26: | ||
<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;"> | <ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;"> | ||
| − | <li>Due to maximum path length limitations during build the build process, source and build folders must be located in a folder with very short total path length. This is expecially critical on Windows. For example, C:\D\S4 for source and C:\D\S4R for release-mode build folder works. | + | <li>Due to maximum path length limitations during build the build process, source and build folders must be located in a folder with very short total path length. This is expecially critical on Windows and MacOS. For example, C:\D\S4 for source and C:\D\S4R for release-mode build folder works on Windows; and /sq5 has been confirmed to work on MacOS. |
</li> | </li> | ||
</ol> | </ol> | ||
| Line 47: | Line 47: | ||
</li> | </li> | ||
| + | <!-- | ||
<li> | <li> | ||
<p>Configure the <code>git svn</code> bridge to ensure the mapping with svn revision.</p><p><strong>git-svn is only required for core developers with svn access - other people can skip it.</strong></p> | <p>Configure the <code>git svn</code> bridge to ensure the mapping with svn revision.</p><p><strong>git-svn is only required for core developers with svn access - other people can skip it.</strong></p> | ||
| Line 82: | Line 83: | ||
4.3.0 22408 trunk | 4.3.0 22408 trunk | ||
| − | ''More corresponding SVN revision numbers can be found [ | + | ''More corresponding SVN revision numbers can be found [[Release_Details|here]] and [http://slicer.kitware.com/midas3/slicerpackages/view here]''. The <tt><MARKER></tt> can be found at the bottom of this page http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=SVNREVISION by replacing <tt>SVNREVISION</tt> with the selected revision. |
''For example, to checkout the source code associated with revision <tt>4.8.1</tt>, you would use the following command:'' | ''For example, to checkout the source code associated with revision <tt>4.8.1</tt>, you would use the following command:'' | ||
| Line 89: | Line 90: | ||
svn co http://svn.slicer.org/Slicer4/branches/Slicer-4-8 Slicer-r26813 -r 26813 | svn co http://svn.slicer.org/Slicer4/branches/Slicer-4-8 Slicer-r26813 -r 26813 | ||
</pre> | </pre> | ||
| + | --> | ||
</ol> | </ol> | ||
Latest revision as of 22:14, 23 March 2020
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:
- While it is not enforced, we strongly recommend you to AVOID the use of SPACES for both the
source directoryand thebuild directory. We mean it.
- Due to maximum path length limitations during build the build process, source and build folders must be located in a folder with very short total path length. This is expecially critical on Windows and MacOS. For example, C:\D\S4 for source and C:\D\S4R for release-mode build folder works on Windows; and /sq5 has been confirmed to work on MacOS.
-
Clone the github repository
cd MyProjects git clone git://github.com/Slicer/Slicer.git
The
Slicerdirectory 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) or use a Git client with a graphical user interface.
