Difference between revisions of "MG/Getting The Code"
(→SVN) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 42: | Line 42: | ||
REMOVE THIS LINE WHEN CONVERTED TO GIT --> | REMOVE THIS LINE WHEN CONVERTED TO GIT --> | ||
| − | == | + | ==GIT== |
| − | If you chose a | + | If you chose a git CLI then run the following command to retrieve the latest source code: |
| − | <pre> | + | <pre>git clone https://github.com/MegaGlest/megaglest-source.git . |
| + | cd megaglest-source | ||
| + | git submodule update --init --recursive</pre> | ||
| + | |||
| + | This will download to the current active folder, so be sure to first navigate to the folder you want to download the GIT project into. | ||
===Project folder layout=== | ===Project folder layout=== | ||
| Line 58: | Line 62: | ||
*[[MG/SVN Structure|SVN Structure]] | *[[MG/SVN Structure|SVN Structure]] | ||
[[Category:MG]] | [[Category:MG]] | ||
| − | |||
Revision as of 01:21, 13 December 2013
NOTE: Due to problems converting to Git, MegaGlest is still using SVN.
GIT
If you chose a git CLI then run the following command to retrieve the latest source code:
git clone https://github.com/MegaGlest/megaglest-source.git . cd megaglest-source git submodule update --init --recursive
This will download to the current active folder, so be sure to first navigate to the folder you want to download the GIT project into.
Project folder layout
Tags and branches
This will check out the trunk directory, which is where active development takes place in. Each release is 'tagged' and a copy resides in the tags directory, so if you wanted an older release you would check out something below instead. Check here to see which ones are available.
Branches are created in the branches subdirectory when required to seperate larger changes from active / stable development, so replace 'trunk' by 'branches' and check with your web brower which ones are available if this is your intention.