Template:Obtaining The Source Code: Difference between revisions
| Line 7: | Line 7: | ||
'''(Bleeding-edge, unstable code for Development and Testing)''' | '''(Bleeding-edge, unstable code for Development and Testing)''' | ||
'''[http://github.com/spring/spring | '''[http://github.com/spring/spring <span style="color:#bbf;">Spring project page at github</span>]''' | ||
<small>[http://status.github.com (status page)]</small> | <small>[http://status.github.com (status page)]</small> | ||
Revision as of 13:11, 28 June 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
There is a branch for MacOS development:
