Azur/README.md

5.3 KiB

Azur: Lephe's game engine

Azur is a game engine for the fx-CG series of graphing calculators that also supports standard PC (SDL2 / OpenGL) and web (emscripten / SDL2 / WebGL) builds.

Azur aims to implement real-world game engine mechanics such as ECS, animation and visual effects, physics, and state serialization. It doesn't try to be super fancy with them, but it does try to get the structure right.

Current status:

  • Build system supporting gint (fxSDK), Linux (SDL 2/OpenGL 3.3) and emscripten (SDL 2/OpenGL ES 2.0)
  • Platform-independent initialization/main loop/etc management.
  • Specialized fragmented-rendering pipeline for gint, providing high-performance graphics.
  • Bare-bones fixed-point computation library.
  • Experimental ECS system under design.

Currently Azur is barely more than the native systems it uses (gint/OpenGL), with no solid unified APIs. It is mostly useful for writing high-performance gint games.

Projects in this repository

The following are Azur libraries:

  • libnum is a C++ fixed-point math library. It provides various sizes of fixed-point values with support for arithmetic, but also some math functions, geometry/linear algebra, and is planned to support numerical algorithms in the future.
  • libazrp is C library that implements Azur's Rendering Pipeline. On fx-CG, Azur uses a very unique rendering method that sacrifices some generality for a significant boost in performance, and this system has uses beyond games. (TODO: Currently still in the azur/ folder)
  • azur is of course the engine itself.

The following external projects are used by some of Azur's features, and maintained as submodules in 3rdparty/:

  • gl3w is a minimalist OpenGL loader, which is used in Azur's OpenGL backend to load the core profile.
  • GLM is math library for graphics, which is interoperable with OpenGL shaders. In the future I hope to use libnum everywhere, but GLM is still useful in OpenGL-related code.
  • Dear ImGui is a GUI library that integrates fantastically with OpenGL. In the future, I plan to provide debugging and introspection for Azur's OpenGL backend using ImGui.

Building

You must install into a different folder for each platform, as the headers would otherwise clash (particulary the auto-generated <azur/config.h>). The library names are different (eg. libazur_emscripten.a), but this is just to avoid confusing errors; the folders must still be different.

Building for fx-CG

Use the fxSDK toolchain. When building with the fxSDK, AZUR_PLATFORM=gint is assumed and the fxSDK sysroot is used to install the library.

% fxsdk build-cg install

Building for Linux

I recommend using a user-writable folder like ~/.local. You can record the path in the environment variable AZUR_PATH_linux, in which case the find module for Azur will pick it up automatically regardless of whether CMake searches that particular folder by default.

% cmake -B build-linux -DAZUR_PLATFORM=linux -DCMAKE_INSTALL_PREFIX="$HOME/.local"
% make -C build-linux install -j$(nproc)

# Later (eg. in ~/.profile):
% export AZUR_PATH_linux="$HOME/.local"

Building for emscripten

You will need the emscripten toolchain. I recommend to use a dedicated install folder since this is essentially a cross-compiling target.

% emcmake cmake -B build-emscripten -D AZUR_PLATFORM=emscripten -DCMAKE_INSTALL_PREFIX="$HOME/.prefix-emscripten"
% make -C build-emscripten install -j$(nproc)

# Later (eg. in ~/.profile):
% export AZUR_PATH_emscripten="$HOME/.prefix-emscripten"

Using in an application

Users building programs with Azur for Linux or emscripten should export the environment variables AZUR_PATH_linux or AZUR_PATH_emscripten as described above. The variable AZUR_PLATFORM should also be set on the command-line with -D during configuration, or hardcoded if the application only supports one target.

The application's CMakeLists.txt can then do:

list(APPEND CMAKE_MODULE_PATH "$ENV{AZUR_PATH_${AZUR_PLATFORM}}/lib/cmake")
find_package(Azur 0.1 REQUIRED)

When using gint, only the find_package() is necessary. The fxSDK handles the rest.

The find module then exports up to three targets that can be linked against: Azur::Azur, Azur::GLM and Azur::ImGui (gint only has the first). The result might look like this:

if(AZUR_PLATFORM STREQUAL gint)
  target_link_libraries(myprogram Azur::Azur)
else() # Linux and emscripten
  target_link_libraries(myprogram Azur::Azur Azur::GLM Azur::ImGui)
endif()

History note

Back in 2021 I made a single repository for this engine, along with other programs that I intended to write with it. At the time I didn't intend to distribute the engine in any serious fashion, but that changed after people expressed interest in playing with After Burner.

I split the original repository in May 2022 with git filter-branch, extracting Azur-related contents to this repository. I patched old commits so they can still be built, but mostly for the sake of preserving history; don't expect to be able to use these early commits out-of-the-box.