C++ Builder

The engine is fully compatible with C++ Builder. The complete engine class API is available from C++ in a natural way. You can use TCastleWindow or TCastleControl from C++, just like from Pascal. See the details in this article.

There are 2 examples in CGE specifically for C++ Builder, using engine API from C++:

For C++ Builder you need to Build the packages for all your target platforms. This means right now: Win32 and Win64 (since C++ Builder doesn’t support other platforms as target).

This is in contrast to usage from Pascal, where it is enough to Install the packages for your Delphi IDE architecture (Win32 or Win64, or both, depending on which IDE you use — new Delphi versions come with 64-bit IDE).

By accident, the above advice comes down to the same 2 platforms (Win32 and Win64) but for different reasons: for C++ the supported target platforms dictate this, while for Pascal the IDE platforms dictate this.

The C++ Builder compatibility is available for C++ Builder versions 11.3 and up.

C++ Builder applications by default require redistribution of Delphi run-time libraries (BPL files) too. This is unrelated to CGE. So you cannot just give your users the resulting EXE file, you need to also provide all the BPL (run-time packages) it uses. If you use CGE, then in addition to RTL and FMX, you will also need to redistribute CGE run-time packages (BPL files).

If you forget to distribute the BPL files along with your EXE, users will see an error message like this:

If you want to avoid it, and have everything contained in one big EXE file, follow this answer: How do I create a stand-alone application in C++Builder. In short (as of RAD Studio 12.0) uncheck in project options

Applications are then compiled into a larger EXE, that is "stand-alone" and does not require BPL files to be distributed.

We have tested the above solution, it works for simple FMX applications and CGE applications using TCastleControl like examples/delphi/cpp_builder/fmx. Below is a screenshot, as you can see in the background we only transferred the EXE file to another computer and the data subdirectory.