Difference between revisions of "WesnothRepository"
VonHalenbach (talk | contribs) m (→Download) |
m (→Browse the code: updated current development) |
||
| Line 10: | Line 10: | ||
== Browse the code == | == Browse the code == | ||
| − | There are currently two main streams of development: trunk (1. | + | There are currently two main streams of development: trunk (1.3.x) and branch (1.2.x). There is also a branch for a Python interface to the AI. You can use your web browser to navigate through the source code: |
http://svn.gna.org/viewcvs/wesnoth/ | http://svn.gna.org/viewcvs/wesnoth/ | ||
Revision as of 14:07, 14 February 2007
|
[edit]Compiling Wesnoth |
Platforms
|
Contents
SVN
Wesnoth development currently uses the Subversion software tool to keep developers in sync with each other. See the SVN book for more on how to use Subversion.
Browse the code
There are currently two main streams of development: trunk (1.3.x) and branch (1.2.x). There is also a branch for a Python interface to the AI. You can use your web browser to navigate through the source code:
http://svn.gna.org/viewcvs/wesnoth/
Download
To check out trunk (About 266 MB at october 2006) into a directory wesnoth:
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth
or to check out the 1.2 branch (About 263 MB at december 2006) into a directory wesnoth-1.2:
svn co http://svn.gna.org/svn/wesnoth/branches/1.2 wesnoth-1.2
More info on the repository: https://gna.org/svn/?group=wesnoth
Update
Do this from inside the wesnoth or wesnoth-1.2 directory where you checked out the repository:
svn update
Note that when you update from Subversion, you should always run 'autogen.sh' if configure.ac or any of the Makefile.am files were changed. It is safest to 'make clean' before updating, then update and finally run 'autogen.sh', 'configure' and 'make'.
You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and configure.ac have not changed. If only minor changes were made then even the 'configure' step is optional.