The Defold build setup

Here we list some relevant build information, in order to make the integrations with your extensions as easy as possible.

Here are some things to consider when you create an extension for the Defold engine. For more general guidelines on how to develop cross platform native code, and also extension/Lua apis, please refer to Native Extensions - Best Practices

C++ version

In the engine itself we use no C++ version higher than C++98. While you may use a higher version to build your extension, bear in mind that a higher version might come with ABI changes. This might make it impossible to use your extension in conjunction with other extensions in the engine or on the asset store.

When creating libraries (such as extensions), it’s good to keep the lowest common denominator as a target.


SDK Versions

For the most accurate list of versions, check the

  • Android: NDK 20r, Build Tools 23.0.2, Api Level 16 for armv7 and Api level 21 for arm64
  • iOS: iPhoneOS13.5.sdk
  • MacOS: MacOSX10.15.sdk
  • Windows: WindowsKits 10.0, Microsoft Visual Studio 2019
  • Linux: Ubuntu 16.04, clang 9, libssl-dev, uuid-dev, libxi-dev, libopenal-dev, libgl1-mesa-dev, libglw1-mesa-dev, freeglut3-dev
  • Html5: Emscripten 1.39.16

C++ version + ABI compatibility

  • Linux: clang 9
  • Android:clang using NDK r20
  • Html5: Emscripten 1.39.16
  • Win32: Microsoft Visual Studio 2019 (clang 9 on build server)
  • iOS/MacOS: apple-clang (clang 9 on build server)

For iOS/MacOS, we use -miphoneos-version-min=8.0 and -mmacosx-version-min=10.7 respectively.

We don’t specify a specific C++ version, so we use the default of each compiler.

Win32 + Clang

A recent addition is to be able to build the Windows builds using clang. This allows for faster builds on our servers, and also allows us to streamline our builds.

Static linkage

The custom engine is built using static linkage. The main reason is that on iOS version < 8, multiple executable binaries in an .ipa aren’t allowed in the app store.

No C++ Exceptions

We don’t make use of any exceptions in the engine. It isn’t generally used in game engines, since the data is (mostly) known beforehand, during development. Removing the support for C++ exceptions decreases executable size and improves the runtime performance.

Did you spot an error or do you have a suggestion? Please let us know on GitHub!