Difference between revisions of "WesnothRepository"
(→Browse the code: the current development branch is 1.5, not 1.3.) |
(→Download) |
||
| Line 19: | Line 19: | ||
More info on the repository: https://gna.org/svn/?group=wesnoth | More info on the repository: https://gna.org/svn/?group=wesnoth | ||
| + | |||
| + | Note that if you are trying for commit access, you must have a developer account on gna, it must be registered as part of the Wesnoth group, and you must | ||
| + | check out with | ||
| + | |||
| + | svn co svn+ssh://svn.gna.org/svn/wesnoth/trunk wesnoth | ||
== Update == | == Update == | ||
Revision as of 20:32, 17 November 2008
|
[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.5.x) and stable branch (1.4.x). Most other branches are only used for a short time to do some testing without disturbing the main development. You can use your web browser to navigate through the source code:
http://svn.gna.org/viewcvs/wesnoth/
Download
To check out trunk into a directory wesnoth (about 281 MB to download and 1.12 GB disk space, including .svn dirs, required as of March 12th 2008):
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth
Or, to check out the 1.4 branch (about 281 MB to download and 1.12 GB to store on disk as of March 12th 20087) into a directory wesnoth-1.4:
svn co http://svn.gna.org/svn/wesnoth/branches/1.4 wesnoth-1.4
More info on the repository: https://gna.org/svn/?group=wesnoth
Note that if you are trying for commit access, you must have a developer account on gna, it must be registered as part of the Wesnoth group, and you must check out with
svn co svn+ssh://svn.gna.org/svn/wesnoth/trunk wesnoth
Update
Do this from inside the wesnoth or wesnoth-1.4 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.