Difference between revisions of "WesnothRepository"
m (→Update) |
m (→Update) |
||
| Line 25: | Line 25: | ||
== Update == | == Update == | ||
| − | Do this from inside the | + | Do this from inside the ''wesnoth'' or ''wesnoth-1.0'' directory where you checked out the repository: |
svn update | svn update | ||
Revision as of 07:43, 12 November 2005
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
You can use your web browser to navigate through the source code:
http://svn.gna.org/viewcvs/wesnoth/
Download
There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth
or to check out the 1.0 branch:
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0
More info on the repository: https://gna.org/svn/?group=wesnoth
Update
Do this from inside the wesnoth or wesnoth-1.0 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 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.