Template:Obtaining The Source Code: Difference between revisions
→Development Sources from Git: removed special OS X repo |
mNo edit summary |
||
| Line 24: | Line 24: | ||
<code><pre>git pull --rebase</pre></code> | <code><pre>git pull --rebase</pre></code> | ||
If github is unavailable or slow, there is a mirror: | If github is unavailable or slow, there is a mirror: | ||
'''git://springrts.git.sourceforge.net/gitroot/springrts/springrts''' | '''git://springrts.git.sourceforge.net/gitroot/springrts/springrts''' | ||
Revision as of 17:50, 11 July 2010
Current
(For playing Spring online)
Using Git is the recommended way to get the sources of the engine.
In spite of, you can use the official tarballs to compile Spring without git.
Note: Do NOT use the zip-files from github, they are missing important data to compile Spring.
See Building spring for build instructions.
Development Sources from Git
(Bleeding-edge, unstable code for development and testing)
Spring project page at github (status page)
Git clone URL for the master repo:
git://github.com/spring/spring.git
For serious developers. This will also allow you to make a patch out of the changes you make to the code, and send it to one of the developers with repository access.
Assuming the GIT command line client is installed, you can clone the repository with
git clone git://github.com/spring/spring.git
and update it with:
git pull --rebase
If github is unavailable or slow, there is a mirror:
git://springrts.git.sourceforge.net/gitroot/springrts/springrts