Last update: December 18, 2021
Quick links:
We try to provide precompiled binaries of SuperTux for a number of platforms. You should check https://supertux.org/download.html for the packages and instructions on how to install them. If there are no prebuilt binaries for your platform, then you might still be able to compile the source code yourself. In this case read the next sections.
We also provide binaries automatically generated as code is added to the repository. These are built using GitHub Actions and are generally used to validate code quality, but as they produce binaries, those can be downloaded and installed like any release. You may find the nightlies at https://download.supertux.org/.
Alternatively, if you have a GitHub account, you may find nightlies directly on GitHub either here for common platforms (Windows, Mac, Linux) or here for the rest (FreeBSD, WASM, Ubuntu Touch); click on any entry in the list on the right (topmost = most recent), then scroll down to the Artifacts section. Note that this only works if you are logged in to GitHub.
Tip: You may take inspiration from the workflow files.
To build SuperTux from source, you need to have a number of tools and libraries installed. Note that most of these things should already be available prepackaged and optimized for your distribution, it is recommended that you check your distribution first before downloading from the websites. You can also check https://github.com/SuperTux/wiki/blob/master/Building-SuperTux.md for up-to-date build instructions for a variety of different platforms and distributions.
build-essential
on Debian-based distros,
base-devel
on Arch-based distros and the Xcode Command Line tools on OS X.cmake
Note I: for any of the above listed libraries (OpenGL, SDL2, SDL2_image,
OpenAL, GLEW/glbinding, Boost, cURL, libogg and libvorbis), you should
also have development headers installed. Debian-based distributions have -devel
packages containing the mentioned headers, on Arch Linux these should be included
in the library package.
Note II: We tried to write our code clean, portable and platform neutral, so it should be possible to compile it on a wide range of platforms and also with other compilers than gcc or clang. We use GitHub Actions to test commits and pull requests in our repository, but unfortunately it's not always possible to test the code in very exotic setups. However, feel free to report issues to our bug tracker on GitHub.
Note III (regarding glbinding): To use glbinding instead of GLEW, call cmake
with the flag -DGLBINDING_ENABLED=ON
For ease of use, here are some installation lines for some Linux distributions:
sudo apt-get update && sudo apt-get install -y cmake build-essential libogg-dev libvorbis-dev libopenal-dev libboost-all-dev libsdl2-dev libsdl2-image-dev libfreetype6-dev libraqm-dev libcurl4-openssl-dev libglew-dev libharfbuzz-dev libfribidi-dev libglm-dev zlib1g-dev
SuperTux uses CMake to generate a set of Makefiles for the build process. To generate these Makefiles and build SuperTux, perform the following steps:
cd
to the directory where you unpacked the SuperTux source
archive, i.e. to the directory containing src
and data
.
If you cloned this Supertux repo using git run git submodule
update --init --recursive
to fetch/update squirrel, tinygettext,
physfs, and some other modules.
(If you got this version of Supertux from a tarball (.tar), squirrel
and tinygettext are already in the tarball.)
Create and change to a new, empty build directory by running mkdir
build
, cd build
.
Run cmake ..
to create the Makefiles needed to build SuperTux
with standard options. If you are missing any libraries needed to
build SuperTux, install those first, then try running CMake again.
See below for instructions on how to change to standard options.
Type make
to start the build process.
Type make install
to install the programs and any data files and
documentation. (You should be a root user on Linux systems. You can
become a root user with the su
command or by using sudo make
install
) Note that there is no uninstall target, so you might wish
to create a package or other system-specific installation instead.
The game should work now and you can remove the source directory.
You can customize the build process by setting additional options for
CMake. The easiest way to do this is to use run ccmake ..
instead of
cmake ..
to bring up the curses-based user interface of CMake.
Select an option using the arrow keys, change the selected option by
pressing the Enter key, then hit the c
(repeatedly, if necessary) to
apply your changes and bring up new options resulting from your newly
set ones. When you are done, press the g
key to generate a new set
of Makefiles and exit.
Alternatively, you can pass options to cmake ..
via the command
line. Some common command line switches are:
-DCMAKE_VERBOSE_MAKEFILE=ON
: Generates Makefiles that print all commands prior to executing them.
-Dxxx_LIBRARY=/path/to/library.so -Dxxx_INCLUDE_DIR=/path/to/headerfiles
: Manually specify the installation directory of a library.
-DCMAKE_BUILD_TYPE=DEBUG
: Enables debug mode and compiles extra debug symbols into the SuperTux executable. This is useful when sending in bug reports to the developers.
-DCMAKE_BUILD_TYPE=RELEASE
: Enables release mode and compiles some sanity checks out of the build.
-DENABLE_DISCORD=ON
: Enables compiling the Discord integration in SuperTux. You may re-disable
the integration later by replacing ON
with OFF
.
SuperTux does not need to be installed on the system; you can run it from its own directory.
If ccache
is installed and working,
it can help to significantly reduce the (re)compilation time,
e.g. when doing a git bisect with many checkouts.
Furthermore, it is possible to reduce the optimization level to O1,
which may reduce compilation times:
cmake .. -DWARNINGS=ON -DCMAKE_CXX_FLAGS="-O1"
A general way to reduce compilation time is running make
with multiple
threads:
make -j $(nproc || sysctl -n hw.ncpu || echo 2)
To build SuperTux on Windows with Visual Studio you need to have CMake and a recent version of Visual Studio installed. Visual Studio 2015 Community Edition is known to work fine.
Because it's difficult to build and download all the dependencies per hand on windows, SuperTux provides a dependency package that should contain all headers and libraries needed to build SuperTux on Windows.
Unpack the SuperTux source pack or get the source with git (git clone --recursive https://github.com/SuperTux/supertux.git
).
Extract the dependency package
into the source directory, so the dependencies
folder is besides the src
folder.
Create a new, empty build
folder.
Open a console window and navigate to the build
directory.
Run cmake ..
to create the VS solution that builds SuperTux with standard options.
For more CMake options, look at end of the Linux/UNIX build section.
Open the new Visual Studio solution SUPERTUX.sln
in the build
directory.
You may also run cmake --build .
instead.
Build the project.
Now you can run SuperTux using the run_supertux.bat file
To compile SuperTux to host on the web, you will need the Emscripten SDK and vcpkg, in addition to the general development tools. Note that you only need the General development tools; you do not need any library, as those are managed with Vcpkg.
Note that you must install and activate the version 1.40.1 of the Emscripten toolchain; newer versions are known not to work properly.
Make sure you have all the submodules if you are using Git:
git submodule update --init --recursive
Patch SDL_ttf by applying the patch in mk/emscripten/SDL_ttf.patch
:
```
git apply mk/emscripten/SDL_ttf.patch
patch -p1 < mk/emscripten/SDL_ttf.patch
2. Install dependencies using Vcpkg (Make sure you enabled Emscripten and ran
`source .../emsdk_env.sh`!):
vcpkg integrate install vcpkg install --target wasm32-emscripten boost-date-time boost-filesystem boost-format boost-locale boost-optional boost-system glbinding libpng libogg libvorbis glm zlib
3. Run CMake using Emscripten's wrapper:
emcmake cmake -DCMAKE_BUILD_TYPE=Release -DENABLE_OPENGLES2=ON -DCMAKE_TOOLCHAIN_FILE=/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake -DVCPKG_TARGET_TRIPLET=wasm32-emscripten -DGLBINDING_ENABLED=ON -DEMSCRIPTEN=1 ..
Replace `/path/to/vcpkg` with the absolute path to where Vcpkg is installed.
Note that Debug builds are generally unplayably slow. Also, the
`-DENABLE_OPENGLES2=ON` flag is optional and will enable using WebGL instead of
the SDL renderer. Currently, the WebGL renderer is much slower than the SDL
renderer.
4. Copy data files to the build folder, as Emscripten will package them to make
them usable from WASM:
rsync -aP ../data/ data/
5. Build SuperTux:
emmake make -j$(nproc || sysctl -n hw.ncpu || echo 2)
6. Replace the Emscripten HTML template with SuperTux's custom container:
rm supertux2.html && cp template.html supertux2.html
You may skip the step above you intend to directly open the `template.html` file;
note that SuperTux won't work if it is not located in the custom template, as it
requires some custom JavaScript functions to work properly.
7. Run the Emscripten webserver:
emrun --no_browser .
You can now play SuperTux by opening `http://localhost:6931/supertux2.html` in
your browser.
Note that if you intend to run SuperTux on a public web server, you must set
[two headers](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#security_requirements)
as a web security requirement.
### Ubuntu Touch using Clickable
To compile for Ubuntu Touch phones, you will need an Ubuntu desktop, as well as
[Clickable](https://clickable-ut.dev/en/latest/install.html). You will not
need any other development library, as those are already managed by Clickable.
First, make sure you have all the submodules:
git submodule update --init --recursive
Then:
- To install SuperTux on your phone, plug your phone to your computer and run:
clickable --config mk/clickable/clickable.json
- To run SuperTux directly on your computer:
clickable desktop --config mk/clickable/clickable.json
- To build SuperTux without running it:
clickable build --config mk/clickable/clickable.json
``
You may specify an architecture using the
--arch ARCHflag. Clickable
currently supports
amd64,
arm64and
armhf`.