WesnothRepository
|
[edit]Compiling Wesnoth |
Platforms
|
The Battle for Wesnoth code-base is stored in a version control repository. Version control allows the entire development team to edit files concurrently. The version control software tracks revisions, stores a record of all edits, and prevents simultaneous editing from causing clashes. All changes are stored in the version control repository.
When a release is planned, the current set of the files in the repository is "frozen", given a version number, and shipped out to the world at large. Then, as files continue to be edited by the developers, the repository code advances past that point. The repository (or "repo") version is by definition the most up-to-date version of the code.
The Wesnoth repository is a Git repository and is hosted on GitHub:
Contents
What is Git?
Are you a newcomer to Git or GitHub who would like to work on Wesnoth? |
|---|
| If so, you may find iceiceice's Git for Wesnoth Crash Course to be a useful read -- while WesnothRepository is also beginner-focused, it's not as extensive as iceiceice's Crash Course). |
Git is the most widely used open-source version-control system. You can learn more about it at its website:
Git replaced Subversion (SVN) as Wesnoth's version-control system in March 2013. Subversion had, itself, previously replaced an older program, Concurrent Versioning System (CVS), in 2005. These earlier systems have left a few traces in the version history which you might encounter; some older documentation and a few files refer to them.
Browse the code
Want a GUI for Git? |
|---|
| SmartGit is cross-platform and supposedly powerful, and the IDEs Qt Creator and Microsoft Visual Studio provide Git GUIs. However, the official Git command-line program is by far the easiest Git program to get help with -- you may well have trouble finding people who can help you with a Git GUI. |
You can use a Web browser to view the source code at the following Web address:
There are currently two main streams of development ("branches"): the master branch (1.19.x), and the stable branch (1.18.x). (1.16.x is now oldstable.) Most other branches are only used for a short time to do some testing without disturbing the main development.
Download
To clone a copy of the repository into a directory named "wesnoth", run this command:
> git clone "https://github.com/wesnoth/wesnoth.git" wesnoth
Technical aside: Git transport protocols |
|---|
There are other transport protocols, in addition to Hypertext Transfer Protocol Secure (HTTPS), over which one can clone a Git repository from GitHub, including:
A more detailed explanation is available here. |
(Note: the ">" sigil represents a command prompt; don't type it in.)
FAQ
Q: The repository is about three gigabytes large, and my Internet connection is not stable enough to reliably download it. What should I do?
- Use a download manager to download the directory "https://github.com/wesnoth/wesnoth.git", in one or more sessions.
- Put this "wesnoth.git" directory, which is the internals of the Wesnoth repository, in a new, empty directory.
- Rename the "wesnoth.git" directory to ".git".
- Finally, run these commands in the directory that contains the ".git" directory:
> git remote add remote "https://github.com/wesnoth/wesnoth.git" > git reset --hard HEAD
The first command links your local repository to the upstream repository; the second checks out a working tree (i.e., copies the files out of the ".git" directory into a form that you can use).
Alternative: This will make a shallow clone and allow you to fetch additional history as desired.
- Start by using a clone command
- Run a git fetch command with an increased depth, such as "git fetch --depth=2000"
- Continue to run additional fetch commands, each time increasing the depth, based on what your connection can handle. As of this writing, the max depth is around 60-70K.
- When an increase in depth no longer brings additional data, verify you have a complete repository by using "git fetch --unshallow"
- To fix the single branch checkout aspect, use git config and fetch commands.
A sample sequence is shown below. You may want to use smaller depth increases (i.e.,2-5K) based on your connection speed and reliability.
> git clone --depth 1 "https://github.com/wesnoth/wesnoth.git" wesnoth > git fetch --depth=10000 > git fetch --depth=20000 > git fetch --depth=30000 > git fetch --depth=40000 > git fetch --depth=50000 > git fetch --depth=60000 > git fetch --depth=70000 > git fetch --unshallow > git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*" > git fetch origin
Q: I don't want any alternate branches or repository history. How could I avoid downloading that?
A: This simply requires a more elaborate command. For example, to only download the last revision of the 1.18 branch, and store it in a directory named "wesnoth-1.18-single-branch-test":
> git clone --branch 1.18 --single-branch --depth 1 "https://github.com/wesnoth/wesnoth.git" wesnoth-1.18-single-branch-test
Example results:
> git clone --branch 1.18 --single-branch --depth 1 "https://github.com/wesnoth/wesnoth.git" wesnoth-1.18-single-branch-test Cloning into 'wesnoth-1.18-single-branch-test'... remote: Counting objects: 20751, done. remote: Compressing objects: 100% (20087/20087), done. remote: Total 20751 (delta 968), reused 11881 (delta 416), pack-reused 0 Receiving objects: 100% (20751/20751), 444.98 MiB | 636.00 KiB/s, done. Resolving deltas: 100% (968/968), done. Checking out files: 100% (20369/20369), done. > du -sh wesnoth-1.18-single-branch-test # "du" means "disk usage". 1.3G wesnoth-1.18-single-branch-test
However, for development and testing, it is often better to have some of the repository history, so that you can quickly check out older versions of the repository to pin down a bug.
Push access
For push access (the capability to push changes from your local repository) to our upstream repository on GitHub, you must have an account on GitHub, which must be registered as part of the Battle for Wesnoth organization.
It may be convenient to use Git's Secure Shell (SSH) transport protocol, so that you needn't either enter your username and password each time you push commits, or insecurely store those credentials in an unencrypted configuration file. To use the SSH transport, you will need to generate an SSH key pair with a command like (on Unix descendent operating systems, including Linux distributions and Apple macOS, at least) this:
> ssh-keygen -t ed25519 -f "<file>" -C "<your name>'s SSH key for GitHub"
On a typical Linux distribution or on Apple macOS, <file> would be, e.g., "~/.ssh/id-key-for-github".
Once you have generated an SSH key pair, put the following into your SSH configuration file (on Unix descendent systems, this is generally "~/.ssh/config"):
Host github.com IdentityFile <file>
Then register the key with GitHub, by going to <https://github.com/settings/ssh>, selecting "Add SSH key", and pasting the contents of the public key file (<file>, but with a ".pub" extension) into the "Key" field.
Then, if you have not yet cloned the repository, clone it via SSH:
> git clone "ssh://git@github.com/wesnoth/wesnoth.git" wesnoth
If you have already cloned the repository, you can set it to use SSH transfer:
> git remote set-url origin "ssh://git@github.com/wesnoth/wesnoth.git"
You can also leave your local repo using the read-only URL, and add a pushurl. Manually editing the .git/config also allows it to be commented-out to avoid accidentally pushing to it instead of a fork:
[remote "origin"] url = https://github.com/wesnoth/wesnoth # pushurl = git@github.com:wesnoth/wesnoth.git fetch = +refs/heads/*:refs/remotes/origin/*
Force-pushing policy
A forced push rewrites a branch tip to point to a new commit without checking first whether the new commit is a descendant of the current tip. This effectively allows you to rewrite the commit history of a branch, which may be useful when working with pull requests from your own personal fork.
> git push --force fork <branch name>
However, for a public repository depended upon by more than a handful people like any of the Wesnoth repositories at <https://github.com/wesnoth>, force-pushing becomes a serious inconvenience that may have negative consequences in some cases, if history is lost in the process. For this reason, force-pushing to the upstream Wesnoth repositories is NOT allowed unless specifically authorized by the repository administrators in order to resolve an urgent issue.
Update
Do this from inside the wesnoth directory:
> git pull
Reviewing your changes
Before committing, it's always wise to run:
> git diff
and look at the output. Some kinds of mistakes that are hard to see embedded in all the code you have modified are more easily spotted in the isolated diff lines.
Generating patches
Under Git on a Unix-like operating system, you'll typically do
> git format-patch HEAD~1..HEAD
or something similar; "HEAD~1" may be replaced by a hash or symbolic reference to any earlier revision. This will produce one or more patch files, numbered and ending with the extension ".patch". See PatchSubmissionGuidelines for more on how to get these merged into the public repository.
Push to your own fork
If you have an account on GitHub, you can fork the repository and add your fork as a remote of your clone.
> git remote add fork git@github.com:YOUR_USERNAME/wesnoth.git
You can then push your branches to your fork:
> git push fork branch_name
Or, if you want to push one branch in your local repository to another in the remote repository:
> git push fork local_branch_name:remote_branch_name
You can then create pull requests from your branches in GitHub’s Web interface.