Latest Posts

Changes in Download

Revision Differences of Revision 79

[TOC] ¶

## Official Builds ¶

### Windows ¶
1. Download the [Windows setup file](https://launchpad.net/widelands/build18/build-18/+download/widelands-build18-win32.exe). ¶
2. Double-click it and follow the instructions. ¶
3. Afterwards simply start Widelands by clicking on one of the generated icons (desktop, start menu, ...). ¶


### Mac OS X ¶
1. Download the [disk image](https://launchpad.net/widelands/build18/build-18/+download/widelands-build18-mac.dmg). ¶
2. Open the Disk Image ¶
3. Copy the executable to your local disk. ¶
4. Double click it to run. ¶


### Linux ¶
It is likely, that there are pre-compiled packages for your distribution. Widelands is packaged in all major Linux distributions. ¶

For Ubuntu, especially for older versions which will not get a backport of the latest build, we offer a [PPA](https://code.launchpad.net/~widelands-dev/+archive/widelands). Follow the install instructions on the PPA's site to add it to your system. ¶

In case your distribution does not provide pre-compiled packages you have to compile Widelands yourself. Go to the [BuildingWidelands](/wiki/Building Widelands) page for further instructions. ¶



## Unofficial development Builds ¶

There are some people providing pre-compiled (ready to run like our official releases) packages, made from our current development state. Below are the links to those builds. Installation should work similar as described in "Official builds" ¶

### Windows ¶
[Tino](/profile/Tino) provides daily (or even more often compiled) builds. These can be found at [http://widelands.8-schuss.de/](http://widelands.8-schuss.de/). ¶

After downloading one of the development builds your browser might warn you that the file can possibly harm your computer. This is a false alarm! There is just too little information about these files, because they change so rapidly, that the browser cannot say for sure whether they are malicious or not. ¶

### Mac OS X ¶

[SirVer](https://wl.widelands.org/messages/compose/SirVer/) builds fairly often 64bit binaries for Mac OS X. You can find them here: ¶

<http://www.widelands.org/~sirver/wl/macos_daily/> ¶

Please report any problems with those via [PM to SirVer](https://wl.widelands.org/messages/compose/SirVer/). ¶

### Linux ¶

#### Arch ¶
__PKGBUILD:__ There is a widelands-bzr pkgbuild in the Arch User Repository: [click here](https://aur.archlinux.org/packages/widelands-bzr/) ¶

#### Ubuntu (recent releases) ¶

The dev team maintains a PPA for Ubuntu on Launchpad with daily builds of the latest development version. ¶
PPA stands for personal package archive - it is essentially something you add to your apt sources.list and which will get queried when you search in the Ubuntu Software Center (or via other alternatives such as apt-get install). It will guarantee that you are using the latest version of Widelands on your system. ¶

Our PPA with daily builds is here: <https://launchpad.net/~widelands-dev/+archive/widelands-daily>. Installing from it is as simple as opening a terminal and typing: ¶

sudo add-apt-repository ppa:widelands-dev/widelands-daily ¶
sudo apt-get update ¶
sudo apt-get install widelands ¶

__PS.__ There are only release builds and release builds with debug info on Launchpad. To use the debug window (F6) you will need to build Widelands in debug mode, see [BuildingWidelands](/wiki/Building Widelands) for a !HowTo on building. ¶

## Source Code ¶

### Release ¶
The source code of build 18 can be [downloaded here](https://launchpad.net/widelands/build18/build-18/+download/widelands-build18-src.tar.bz2). ¶


### Development version ¶
If you plan to join development or are just interested in the latest inventions ¶
you should go for this. You __need to have__ Bazaar (bzr) installed, to check-out the trunk. Type in the ¶
console: ¶

~~~ ¶
bzr branch lp:widelands ¶
~~~ ¶

After downloading the source, head over to [BuildingWidelands](/wiki/Building Widelands) for a !HowTo on building.

#### Troubleshooting ¶

If you have problems getting the sources, failing with a message like "Unable to negotiate with <IP>: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1": This is probably because you are using a new version of OpenSSH (>= 7.0), which has it disabled as default because of security reasons. You can add the following lines into your /etc/ssh/ssh_config file (on Linux at least, don't know about Windows or MacOS): ¶

~~~ ¶
Host bazaar.launchpad.net ¶
KexAlgorithms +diffie-hellman-group1-sha1 ¶
~~~ ¶

This enables the old encryption method for the very specific host where Launchpad hosts its sources, while not allowing it for other hosts, thus not compromising your overall security too much. Hopefully, those guys at Launchpad are fixing the encryption soon.