Skip to content

Build Configurations

There are several build configurations of the Blamite Game Engine which exist. Not all of these are publicly accessible, however each will have slightly different characteristics and tools available.

Understanding Build Configurations#

Blamite build configurations are slightly more complicated than the standard "Debug/Release" configurations that most projects will offer. However, most of these configurations are fairly straightforward.

All configuration names are made up of two "keywords", which indicate what type of build is present, such as tag test or cache release. The first keyword refers to the type of content supported, whereas the second more precisely refers to the configuration - and typically correlates strongly to the standard debug/release found in other software projects.

The first keyword can be either of the following values:

  • tag - This indicates that game content will be loaded from loose tag files, rather than cache files. Loading from tags is often much slower than cache files, but allows for tags to be edited individually with ease. As such, engine builds intended for game developers will often include at least one tag executable.
  • cache - This indicates that game content will only be loaded from cache files, and NOT from loose tags.

The second keyword can be one of the following values:

  • debug - This indicates the game is a debug build, intended for engine development and debugging. These do not have any compiler optimizations, and as such will typically perform much worse than a test or release build. These builds are intended for engine development only, and are typically not released to the public.
  • test - This indicates the game is a test build, intended for testing. These are built with compiler optimizations, and as such can perform close to release builds. However, these will still have debugging features enabled by default, allowing for easier diagnosing of issues. These builds are available for game developers using Blamite as their engine of choice.
  • release - This indicates the game is a release build. No debugging features or utilities are enabled by default, though some projects may choose to allow some debugging tools to be enabled via command-line arguments. Additionally, this configuration cannot be used with tags - as such, the only possible configuration which can be a release build is cache release. These builds are typically used for shipped executables, available to end users.

Comprehensive Configuration List#

Below is a list of all currently supported engine build configurations.

Configuration Name Details
cache release Cache release build. Used for shipped games.
cache test Cache testing build. Used for game development.
cache debug Cache debug build. Used for engine development.
tag test Tag testing build. Used for game development.
tag debug Tag debug build. Used for engine development.