|
|
| (13 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| == Building OpenClonk in four easy steps. ==
| | * [[Build OpenClonk]] |
| | | * [[Git Workflow]] |
| 1. Install Mercurial and TortoiseHG
| | * [[Style Guidelines]] |
| | | * [[Source code structure]] |
| http://bitbucket.org/tortoisehg/stable/wiki/install
| | * [[Sync losses]] |
| | |
| Linux users should install the mercurial package from their distribution first. Technically, you can skip installing TortoiseHG, but the GUI changelog is just so much better than the text one.
| |
| | |
| 2. Get the source code
| |
| | |
| Use the TortoiseHG dialog to clone http://hg.openclonk.org/ or execute this command in a commandline shell:
| |
| <nowiki>hg clone http://hg.openclonk.org/ openclonk</nowiki>
| |
| | |
| 3. Install Build tools and libraries
| |
| | |
| Please refer to the Readme.*.txt in the freshly checked out source tree.
| |
| For windows, we provide prebuilt packages of libraries:
| |
| * http://forum.openclonk.org/topic_show.pl?pid=1405#pid1405 for Microsoft C++ users | |
| * http://forum.openclonk.org/topic_show.pl?pid=1522#pid1522 for GNU Compiler Collection users | |
| | |
| 4. Compile the game
| |
| | |
| == Get your change into the openclonk.org repository ==
| |
| | |
| First, change the source code. Then commit it to your local mercurial repository. Then, export the commit as a patch (if you only changed source code or text) or as a bundle (if you changed binary files). Then attach the file to a forum post.
| |
| | |
| == Miscellanous notes ==
| |
| | |
| We have [[SourceCodeReorganization|reorganized the source code]].
| |
