- 1 Compiling Wesnoth
- 2 Prerequisites
- 3 Source Code
- 4 Compiling
- 5 Install / Uninstall
- 6 Running the game without installing
- 7 See also
This page covers compilation on a Unix-like system, using the scons and cmake build systems.
- Compiling Wesnoth on Windows
- Compiling Wesnoth on FreeBSD
- Compiling Wesnoth on macOS
- Compiling Wesnoth on Syllable
- Compiling Wesnoth on SuSE -For install on SuSE 10.0
Forcemstr has cross compiled for Windows using the free mingw32 tools, running under Linux.ref ?
For detailed instructions and full prerequisites, please consult the current INSTALL file in the source code.
You need a C++ compiler (such as gcc).
You must have the following libraries installed on your system to build Wesnoth 1.14. Many Linux distributions split development packages from libraries. If so, you need to have the development packages to build Wesnoth (the -dev packages include the header files which are required to build packages from source). You will also need the runtime packages to actually run Wesnoth.
- libsdl >= 2.0.4 (https://www.libsdl.org/)
- sdl-image >= 2.0.0 (with PNG and JPEG support) (https://www.libsdl.org/projects/SDL_image/)
- sdl-mixer >= 2.0.0 (with Vorbis support) (https://www.libsdl.org/projects/SDL_mixer/)
- sdl-ttf >= 2.0.12 (https://www.libsdl.org/projects/SDL_ttf)
- libboost >= 1.50.0 (https://www.boost.org/)
- If your distro splits boost, you need: boost_filesystem, boost_iostreams, boost_locale, boost_random, boost_regex, boost_asio, boost_program_options, boost_system, boost_thread.
- You need gzip and bzip2 support in boost_iostreams
- You must use the icu backend of boost_locale
- libcrypto (https://wiki.openssl.org/index.php/Libcrypto_API)
- bzip2 (http://www.bzip.org/)
- zlib (in theory already needed for libsdl-image, http://www.zlib.org/)
- libvorbisfile (https://xiph.org/vorbis/)
- pangocairo >= 1.22.0 (http://www.pango.org/)
- cairo >= 1.10.0 (https://www.cairographics.org/)
- libfontconfig >= 2.4.1 (https://www.freedesktop.org/software/fontconfig/front.html)
The following libraries are optional.
- libdbus-1 (only required desktop notifications, https://www.freedesktop.org/wiki/Software/dbus)
- libreadline (command history and history expansion in the built-in Lua console)
- fribidi >= 0.10.9 (only required for RTL languages)
Dev Version Additional Requirements
For Wesnoth 1.15, the following are additionally required:
- C++14 capable compiler (GCC 5.0/Clang 3.8 or above)
- libboost >= 1.56.0
- sdl-ttf is no longer required
To be able to build things, you will need a build tool, either
- scons >=1.0 (https://www.scons.org/)
- cmake >=2.8.5 (https://www.cmake.org/)
Linux Tips to Easily Gather Dependencies
On all Linux distributions that are based on Debian (like e.g. Ubuntu, Linux Mint) it may be enough to use these commands if your distribution ships a recent version of Wesnoth. (However dependencies might be outdated for building the Development version or building Stable versions newer than are shipped with your distribution. In those case you will need to install the additional dependencies by hand after running the following commands):
sudo apt build-dep wesnoth-1.12 sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libboost-all-dev libvorbis-dev libcairo2-dev libpango1.0-dev libssl-dev libreadline-dev cmake make scons pkgconf
For testing purposes wesnoth uses Docker images, you can also have a look at which packages are installed by them here. (Though note that your system may use different version numbers.)
The following command will install the prerequisites for Wesnoth 1.14 in openSuSE. All dependencies are in the standard OSS repository.
sudo zypper install libSDL2-devel libSDL2_image-devel libSDL2_mixer-devel libSDL2_ttf-devel boost-devel libopenssl-devel libbz2-devel zlib-devel libvorbis-devel pango-devel cairo-devel fontconfig-devel dbus-1-devel readline-devel fribidi-devel gettext-runtime cmake make scons pkg-config
The following command will install the prerequisites for Wesnoth 1.14 in CentOS, RedHat or Fedora. All dependencies are in the standard OSS repository. You may use
yum instead of
sudo dnf install SDL2-devel SDL2_image-devel SDL2_mixer-devel SDL2_ttf-devel boost-devel openssl-devel bzip2-devel zlib-devel libvorbis-devel pango-devel cairo-devel fontconfig-devel dbus-devel readline-devel fribidi-devel gettext cmake make scons pkgconf-pkg-config
This command installs the prerequisites for Wesnoth 1.14 in Arch Linux.
sudo pacman -S sdl2 sdl2_image sdl2_mixer sdl2_ttf boost-libs openssl bzip2 zlib libvorbis pango cairo fontconfig dbus readline fribidi boost gettext cmake make scons pkgconf
You can get it here:
scons is a better choice for beginners, because it requires less configuration and it is more widely used and tested. cmake is used primarily for making certain releases, and is not as well tested.
If any config checks fail, look in the respective log files (eg in build/config.log when using scons) for details. When using scons, a check can spuriously fail due to caching. If this happens, please use --config=force to force its rerun.
Building with SCons
To build using SCons, simply type
in the Wesnoth top-level directory. This will perform the equivalent of "configure --enable-editor --enable-tools; make" under autotools, buiding all client-side tools. To find out more about build options, type
$ scons --help
Equivalents of many configure options will be available, and you can easily build individual targets such as wesnothd.
Because scons checks for out-of-dateness with MD5 checksums of a target's ancestors and its build environment (including compiler and linker flags), the "make clean" and "make uninstall" preliminaries that you need for safety under autotools won't be necessary.
Good options to use with scons are
- This uses clang instead of gcc, which is empirically significantly faster (about 2x)
- Enables ccache.
- If you have ccache available on your system, and you are using git, then this is highly recommended, it can enable you to switch branches and rebuild in minutes.
- build=release vs. build=debug
- Determines whether you build with -O3 optimizations, or -O0 with debugging symbols.
- Keep in mind this preference, like the others mentioned, are "sticky" and will be remembered in the future.
- -j 2, or --jobs 4, etc.
- Build parallelism: This tells scons to run multiple compilation steps in parallel. The number of jobs you tell it to run at once should not be larger than the number of cores that you have.
Building with CMake
CMake supports so called "out of tree" builds. That is you compile in a place completely different from the folder where your checkout is in. To do so, simply create a folder to compile in and call cmake with the path to your checkout. Of course you can also just call cmake from the checkout folder with a plain cmake ., but this is boring, isn't it?
To have cmake build wesnoth in a new dir called cmake_build_dir, just use these commands (PATH/TO/WESNOTH/TOPLEVEL-DIR means the base of your repository checkout or the folder where you extracted the tarball to, not src/ in there!):
$ mkdir cmake_build_dir $ cd cmake_build_dir $ cmake PATH/TO/WESNOTH/TOPLEVEL-DIR
This will perform the equivalent of "configure --enable-editor --enable-server" under autotools. To get an interface for editing settings, just type
$ ccmake .
in the cmake_build_dir. When done with your changes hit 'c' to configure and 'g' to generate the files and exit. In general you can either add commands to your cmake PATH/TO/WESNOTH/TOPLEVEL-DIR call, or change the parameters later on via ccmake or a cmake gui. Equivalents of many configure options are be available.
In the 2nd step you just have to build the game. This is done as with autotools using
This by default builds all the targets you activated. If you want to you can also just build specific targets like wesnothd.
Because CMake checks for out-of-dateness, the "make clean" and "make uninstall" preliminaries that you need for safety under autotools won't be necessary.
Install / Uninstall
Become superuser, so that you have permission to install or uninstall.
$ su Password: /*doesn't show*/
Now that you have permission, proceed
If you are using SCons, install with:
# scons install
And uninstall with:
# scons uninstall
If you are using CMake, installing basically happens the same way as when using autotools. When authorized as admin (see above), just type this:
# make install
Running the game without installing
After compiling it is also possible to just run the game without installing it. All you have to do is execute the compiled binary and provide the path to the data location as argument. This looks e.g. like this:
or, if you compiled outside the place where you have your repository checkout or the extracted tarball (lets assume this content lies in ../wesnoth-1.14):
$ ./wesnoth ../wesnoth-1.14/