Template:Obtaining The Source Code: Difference between revisions
mNo edit summary |
|||
| Line 14: | Line 14: | ||
====Latest Stable (master branch)==== | ====Latest Stable (master branch)==== | ||
Assuming the GIT command line client is installed, you can clone the repository with | Assuming the GIT command line client is installed, you can clone the repository with | ||
<pre>git clone --recursive git://github.com/spring/spring.git -b master</pre> | |||
and update it with: | and update it with: | ||
<pre>git pull --rebase</pre> | |||
====Bleeding-edge (develop branch)==== | ====Bleeding-edge (develop branch)==== | ||
Revision as of 01:29, 23 November 2018
Tarballs
(For playing 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.
Git
Master repo URI:
git://github.com/spring/spring.git
Backup repo: git://git.code.sf.net/p/springrts/code
Latest Stable (master branch)
Assuming the GIT command line client is installed, you can clone the repository with
git clone --recursive git://github.com/spring/spring.git -b master
and update it with:
git pull --rebase
Bleeding-edge (develop branch)
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. If you are new to git and github, you may want to have a look at this guide to get you started.
Just as above with a minimal change: <syntaxhighlight lang="bash">git clone --recursive git://github.com/spring/spring.git -b develop </syntaxhighlight> and update with: <syntaxhighlight lang="bash">git pull --rebase </syntaxhighlight>
Note: you can switch branches this way:<syntaxhighlight lang="bash">
- backup your current changes
git stash
- switch branch
git checkout $MY_OTHER_BRANCH
- sometimes needed
- note, it deletes all your unstashed changes and all non-pushed commits on the new branch,
- but it doesn't delete untracked files.
- git reset --hard
- update/sync with remote repo
git pull --rebase
- optional
- git stash pop # reapplies your changes and DELETES the backup
- or
- git stash apply --index 0 # reapplies your changes and keep the backup (see `git stash list`)
</syntaxhighlight>
Submodules
To obtain the submodules you should clone the repository with --recursive as mentioned above. If you haven't done this, you can execute the following code <syntaxhighlight lang="bash"> git submodule sync git submodule update --init
</syntaxhighlight>
To update the submodules, you have to execute the same commands again or pull normally.