Skip to content
Aeon Games Flagship Game Engine
C++ CMake Python HTML Shell C JavaScript
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.

AeonEngine MS Visual C++ Build status MinGW64 Build status Build Status CodeFactor Patreon Ko-Fi

Aeon Games Flagship Game Engine

Follow us on Facebook

Read about development status and more at Patreon

Aerin just chilling

This is the 3rd iteration of the engine, the first one was started circa 1996 and was lost on a hard drive crash, the second one was started circa 2001 and still exists, but is a mess and a patchwork of collected ideas of 15 years of trying to keep up.



Visual Studio Code with MSYS2 MinGW

You do not need to install Visual Studio Code just to build the project, but it is highly recomended that you do so if you intend on changing the code, or if you want to develop a game using MSYS2/MinGW.

Install MSYS2

Go to MSYS2 and install MSYS2, while the 32 bit version of the MinGW compiler should work, development is focused on 64 bit, so get that if you don't know what to chose.

Install required Packages

Bring up an MSYS2 bash terminal for MinGW and update all of your installed packages:

pacman -Syuu --no-confirm

Follow the instructions, you may have to forcefully shut down the terminal and run the same command at least one time. After pacman reports no more updates, its time to install all our engine dependencies:

pacman -S --needed --noconfirm astyle git sed global mingw-w64-x86_64-make mingw-w64-x86_64-gdb mingw-w64-x86_64-cmake mingw-w64-x86_64-vulkan mingw-w64-x86_64-qt5 mingw-w64-x86_64-protobuf mingw-w64-x86_64-zlib mingw-w64-x86_64-libpng mingw-w64-x86_64-glslang mingw-w64-x86_64-portaudio mingw-w64-x86_64-libogg mingw-w64-x86_64-libvorbis mingw-w64-x86_64-python3 mingw-w64-x86_64-python3-pip mingw-w64-x86_64-python3-numpy

Install autopep8 and cmake-format (optional, only if you want to create a pull request, or make changes to your own fork)

The CMake script installs a git pre-commit hook to format code using astyle, autopep8 (for the Blender scripts) and cmake-format, so you will need these if you want to create any commits.

python3 -m pip install autopep8 cmake-format

Clone this repo

There is no master release branch, so master is development at the moment, so just grab master.

git clone

Initial CMake configuration

Create a build directory inside the repo, I use mingw64, but you can use anything you want, or build outside the repo.

cd AeonEngine
mkdir mingw64
cd mingw64

Run CMake

cmake -G"MSYS Makefiles" ..


Run Make


If everything goes well you'll now have all binary targets build at ming64/bin.

Visual Studio Code

You can now use the "Open Folder" option in VS Code to open the topmost repo folder and then go to View->Terminal, where you'll get prompted to allow bash to run, accept and now you can issue your make commands directly from inside VS Code.

You should be able to run the various executables directly from the terminal or from the debug environment, if you run them from the debug environment they will be run through GDB, so you can set breakpoints or issue commands from the Debug Console.

Ubuntu 14.04 and up

Install Packages

sudo apt-get install -y sed python python3 python-autopep8 python-pep8 python3-pep8 tar wget cmake autoconf automake libtool curl make g++ unzip zlib1g-dev libpng12-dev vim-common qtbase5-dev astyle

Install GCC 8.x (required for c++17)

sudo add-apt-repository --yes ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get upgrade --allow-unauthenticated
sudo apt-get install -y build-essential software-properties-common
sudo apt-get install -y gcc-snapshot
sudo apt-get install -y gcc-8 g++-8
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 60 --slave /usr/bin/g++ g++ /usr/bin/g++-8

Build and install libprotobuf-dev from source

tar -xzvf v3.1.0.tar.gz
cd protobuf-3.1.0
sudo make install
sudo ldconfig
cd ..

Build and install glslang from source

git clone
cd glslang
git checkout 8f674e821e1e5f628474b21d7fe21af2e86b5fb4
mkdir build
cd build
cmake -G "Unix Makefiles" ..
sudo make install
sudo ldconfig
cd ../..

UBUNTU 14.x: Locally install libvulkan-dev from self extracting executable into home directory

cd ~/
chmod a+x
echo "VULKAN_SDK=$PWD/VulkanSDK/" >> ~/.bashrc
echo "export VULKAN_SDK" >> ~/.bashrc
echo "export PATH=$PWD/VulkanSDK/$PATH" >> ~/.bashrc
echo "export LD_LIBRARY_PATH=$PWD/VulkanSDK/$LD_LIBRARY_PATH" >> ~/.bashrc
echo "export VK_LAYER_PATH=$PWD/VulkanSDK/" >> ~/.bashrc
source ~/.bashrc
sudo ldconfig

UBUNTU 16.x: Use apt to install Vulkan SDK

sudo apt-get install -y libvulkan-dev

Generate Makefiles with CMake

cmake -G "Unix Makefiles" .



Visual Studio 2017 (version 15.7 or later is required due to c++17's filesystem dependency) and up

Building with Visual Studio is somewhat more involved as all dependencies and tools need to be build first. The official way of doing this is to use Microsoft's vcpkg, however if you are proficient at building software you can build each dependency individually or you could just find official Windows distributions and install them. You can also pick and chose on what to build and what to install from a previously build distribution, in fact it is recommended to install the Qt5 sdk rather than build it if you want to save about 4+ hours of your life.

Install VCPKG

See Microsoft's vcpkg for instructions, you can clone the repo anywhere, but I suggest c:\vcpkg to keep it global.

Install Engine dependencies

In a command prompt window move to the vcpkg root and run the following command:

.\vcpkg install protobuf zlib libpng glslang spirv-tools

IF and only IF you have time to space and want to debug Qt5 issues, add qt5 to the list:

.\vcpkg install protobuf zlib libpng glslang spirv-tools qt5

Install the Vulkan SDK

Download and install the Vulkan SDK from the LunarG website. The engine supports OpenGL rendering and use of one API or the other is optional, while you could eventually chose not to build either of the renderers, as it is right now, both of them must be built. This is just an oversight rather than a strict policy, and support for disabling modules will be written in the future.

Install the Qt5 SDK (Only if you did not build Qt5 with VCPKG)

Download and install the Qt5 SDK, you may install it anywhere you want, but in general it is a good idea to avoid paths with spaces in it.

Generate solution and project files with CMake

If you're using the GUI, make sure that you add the CMAKE_TOOLCHAIN_FILE variable to point to the vcpkg.cmake file. And if you did not build the Qt SDK, set the variable Qt5_DIR to <Qt5 SDK root>/lib/cmake/Qt5 before pressing the configure and generate buttons. If you're generating them from the CLI, add the paths to the cmake command:

cmake -DCMAKE_TOOLCHAIN_FILE:filepath=<VCPKG ROOT>/scripts/buildsystems/vcpkg.cmake -DQt5_DIR:path=<Qt SDK Root>/lib/cmake/Qt5 <PATH TO ENGINE SOURCE ROOT>


cmake -DCMAKE_TOOLCHAIN_FILE:filepath=<VCPKG ROOT>/scripts/buildsystems/vcpkg.cmake <PATH TO ENGINE SOURCE ROOT>

In No Way Complete TODO List

  • Find out how to use google::protobuf::TextFormat::Parser so raw mesh bytes can be printed and parsed in a more human readable way.
  • Implement a visual programming language gui for shader program authoring (like blueprints).

Unasked Questions Nevertheless Answered (UQNA)

Why do you use protobuf for your data files?

Because I've always felt human readability is not worth the price you pay in performace.

Why do you keep PB plain text files around then?

They're easier to modify. The idea is that you convert them to binary once you're ready to ship.

You could do that with <insert favorite human readable format, usually JSON> which is nicer, so why don't you?

PB's text files are a build in feature, anything else would require a tool to either convert to it, directly to binary protocol buffers or use a proprietary format. That takes time and Google already solved the problem. Do feel free to write your own convertion tool though.

Why are there so many "Linux Build Fix" commits?

I develop on Windows first and then make sure things work properly on Linux. Things sometimes break. While I do not hold a particular preference towards Windows, there are some things that keep me working on it:

  • Visual Studio's Debugger is the best there is. I do know how to use gdb, but I am not as proficient with it as with VS, -and I am yet to find a graphical frontend I like for it-. (UPDATE) I found VS Code, which is great, in fact it is now the official development environment for the engine, as it makes it the same on Windows (using msys2 and mingw64) as it is on Linux.

  • Most PC gamers game on Windows, that's probably not going to change anytime soon.

  • Windows is the OS I spend most time on, I tend to use a lot of open source code that was born on Linux, but most of it has native Windows ports, shout out to MSYS2, which completelly replaced Cygwin on my setup.

You can’t perform that action at this time.