Build

Table of Contents

• A Note About Version Numbers
• Windows
• Linux
• Android
• macOS/OS X

A Note About Version Numbers

In order to communicate with each other, the server and all clients need to share the same version number. Servers and clients whose version numbers are 0 bypass this check. In any case, they might not function properly with each other if built from different codebases.

If you intend to play using the official builds, for example, ensure that you're on the same codebase by checking out the release tag. You can see these tags here or by typing git tag --sort -v:refname. You also should override the version numbering in the build scripts, as by default the current compile date (not the tag/release/etc.) is used to generate the version number.

For example, to create builds which share the same codebase with the February 18th 2020 official builds, check out the corresponding release tag, being in the SeriousProton directory:

git checkout EE-2020.02.18

and do the same for the EmptyEpsilon directory.

It is easy enough, regardless of which platform/OS you are using, to add some defines to the end of the CMake command in the build process and override the version number which will be generated.

Following the example above, add the following defines to the end of the relevant CMake line (after a space):

-DCPACK_PACKAGE_VERSION_MAJOR=2020 -DCPACK_PACKAGE_VERSION_MINOR=02 -DCPACK_PACKAGE_VERSION_PATCH=18

Those who wish to explore other options for setting the version number should see issue #221 for further discussion.

Windows

Windows Instructions

Linux

• For any debian based distribution: Build from sources Debian Linux (This includes Debian, Ubuntu, and Rasbian for the Raspberry PI)
• Fedora Linux Instructions
• OpenSuSE Linux Instructions

Android

Android build Instruction

OS X

OS X instructions