GDExtension C++ example

Introduction

The C++ bindings for GDExtension are built on top of the C GDExtension API and provide a nicer way to “extend” nodes and other built-in classes in Godot using C++. This new system allows the extension of Godot to nearly the same level as statically linked C++ modules.

You can download the included example in the test folder of the godot-cpp repository on GitHub.

Setting up the project

There are a few prerequisites you’ll need:

See also Compiling as the build tools are identical to the ones you need to compile Godot from source.

You can download the godot-cpp repository from GitHub or let Git do the work for you. Note that this repository has different branches for different versions of Godot. GDExtensions will not work in older versions of Godot (only Godot 4 and up) and vice versa, so make sure you download the correct branch.

Note

To use GDExtension you need to use the godot-cpp branch that matches the version of Godot that you are targeting. For example, if you’re targeting Godot 4.1, use the 4.1 branch, which is what is shown through out this tutorial.

The master branch is the development branch which is updated regularly to work with Godot’s master branch.

Warning

Our long-term goal is that GDExtensions targeting an earlier version of Godot will work in later minor versions, but not vice-versa. For example, a GDExtension targeting Godot 4.2 should work just fine in Godot 4.3, but one targeting Godot 4.3 won’t work in Godot 4.2.

However, GDExtension is currently experimental, which means that we may break compatibility in order to fix major bugs or include critical features. For example, GDExtensions created for Godot 4.0 aren’t compatible with Godot 4.1 (see Updating your GDExtension for 4.1).

If you are versioning your project using Git, it is recommended to add it as a Git submodule:

  1. mkdir gdextension_cpp_example
  2. cd gdextension_cpp_example
  3. git init
  4. git submodule add -b 4.1 https://github.com/godotengine/godot-cpp
  5. cd godot-cpp
  6. git submodule update --init

Alternatively, you can also clone it to the project folder:

  1. mkdir gdextension_cpp_example
  2. cd gdextension_cpp_example
  3. git clone -b 4.1 https://github.com/godotengine/godot-cpp

Note

If you decide to download the repository or clone it into your folder, make sure to keep the folder layout the same as we’ve setup here. Much of the code we’ll be showcasing here assumes the project has this layout.

If you cloned the example from the link specified in the introduction, the submodules are not automatically initialized. You will need to execute the following commands:

  1. cd gdextension_cpp_example
  2. git submodule update --init

This will initialize the repository in your project folder.

Building the C++ bindings

Now that we’ve downloaded our prerequisites, it is time to build the C++ bindings.

The repository contains a copy of the metadata for the current Godot release, but if you need to build these bindings for a newer version of Godot, simply call the Godot executable:

  1. godot --dump-extension-api

The resulting extension_api.json file will be created in the executable’s directory. Copy it to the project folder and add custom_api_file=<PATH_TO_FILE> to the scons command below.

To generate and compile the bindings, use this command (replacing <platform> with windows, linux or macos depending on your OS):

The build process automatically detects the number of CPU threads to use for parallel builds. To specify a number of CPU threads to use, add -jN at the end of the SCons command line where N is the number of CPU threads to use.

  1. cd godot-cpp
  2. scons platform=<platform> custom_api_file=<PATH_TO_FILE>
  3. cd ..

This step will take a while. When it is completed, you should have static libraries that can be compiled into your project stored in godot-cpp/bin/.

Note

You may need to add bits=64 to the command on Windows or Linux.

Creating a simple plugin

Now it’s time to build an actual plugin. We’ll start by creating an empty Godot project in which we’ll place a few files.

Open Godot and create a new project. For this example, we will place it in a folder called demo inside our GDExtension’s folder structure.

In our demo project, we’ll create a scene containing a Node called “Main” and we’ll save it as main.tscn. We’ll come back to that later.

Back in the top-level GDExtension module folder, we’re also going to create a subfolder called src in which we’ll place our source files.

You should now have demo, godot-cpp, and src directories in your GDExtension module.

Your folder structure should now look like this:

  1. gdextension_cpp_example/
  2. |
  3. +--demo/                  # game example/demo to test the extension
  4. |
  5. +--godot-cpp/             # C++ bindings
  6. |
  7. +--src/                   # source code of the extension we are building

In the src folder, we’ll start with creating our header file for the GDExtension node we’ll be creating. We will name it gdexample.h:

  1. #ifndef GDEXAMPLE_H
  2. #define GDEXAMPLE_H
  4. #include <godot_cpp/classes/sprite2d.hpp>
  6. namespace godot {
  8. class GDExample : public Sprite2D {
  9.     GDCLASS(GDExample, Sprite2D)
  11. private:
  12.     double time_passed;
  14. protected:
  15.     static void _bind_methods();
  17. public:
  18.     GDExample();
  19.     ~GDExample();
  21.     void _process(double delta) override;
  22. };
  24. }
  26. #endif

There are a few things of note to the above. We include sprite2d.hpp which contains bindings to the Sprite2D class. We’ll be extending this class in our module.

We’re using the namespace godot, since everything in GDExtension is defined within this namespace.

Then we have our class definition, which inherits from our Sprite2D through a container class. We’ll see a few side effects of this later on. The GDCLASS macro sets up a few internal things for us.

After that, we declare a single member variable called time_passed.

In the next block we’re defining our methods, we have our constructor and destructor defined, but there are two other functions that will likely look familiar to some, and one new method.

The first is _bind_methods, which is a static function that Godot will call to find out which methods can be called and which properties it exposes. The second is our _process function, which will work exactly the same as the _process function you’re used to in GDScript.

Let’s implement our functions by creating our gdexample.cpp file:

  1. #include "gdexample.h"
  2. #include <godot_cpp/core/class_db.hpp>
  4. using namespace godot;
  6. void GDExample::_bind_methods() {
  7. }
  9. GDExample::GDExample() {
  10.     // Initialize any variables here.
  11.     time_passed = 0.0;
  12. }
  14. GDExample::~GDExample() {
  15.     // Add your cleanup here.
  16. }
  18. void GDExample::_process(double delta) {
  19.     time_passed += delta;
  21.     Vector2 new_position = Vector2(10.0 + (10.0 * sin(time_passed * 2.0)), 10.0 + (10.0 * cos(time_passed * 1.5)));
  23.     set_position(new_position);
  24. }

This one should be straightforward. We’re implementing each method of our class that we defined in our header file.

Note our _process function, which keeps track of how much time has passed and calculates a new position for our sprite using a sine and cosine function.

There is one more C++ file we need; we’ll name it register_types.cpp. Our GDExtension plugin can contain multiple classes, each with their own header and source file like we’ve implemented GDExample up above. What we need now is a small bit of code that tells Godot about all the classes in our GDExtension plugin.

  1. #include "register_types.h"
  3. #include "gdexample.h"
  5. #include <gdextension_interface.h>
  6. #include <godot_cpp/core/defs.hpp>
  7. #include <godot_cpp/godot.hpp>
  9. using namespace godot;
  11. void initialize_example_module(ModuleInitializationLevel p_level) {
  12.     if (p_level != MODULE_INITIALIZATION_LEVEL_SCENE) {
  13.         return;
  14.     }
  16.     ClassDB::register_class<GDExample>();
  17. }
  19. void uninitialize_example_module(ModuleInitializationLevel p_level) {
  20.     if (p_level != MODULE_INITIALIZATION_LEVEL_SCENE) {
  21.         return;
  22.     }
  23. }
  25. extern "C" {
  26. // Initialization.
  27. GDExtensionBool GDE_EXPORT example_library_init(GDExtensionInterfaceGetProcAddress p_get_proc_address, const GDExtensionClassLibraryPtr p_library, GDExtensionInitialization *r_initialization) {
  28.     godot::GDExtensionBinding::InitObject init_obj(p_get_proc_address, p_library, r_initialization);
  30.     init_obj.register_initializer(initialize_example_module);
  31.     init_obj.register_terminator(uninitialize_example_module);
  32.     init_obj.set_minimum_library_initialization_level(MODULE_INITIALIZATION_LEVEL_SCENE);
  34.     return init_obj.init();
  35. }
  36. }

The initialize_example_module and uninitialize_example_module functions get called respectively when Godot loads our plugin and when it unloads it. All we’re doing here is parse through the functions in our bindings module to initialize them, but you might have to set up more things depending on your needs. We call the function register_class for each of our classes in our library.

The important function is the third function called example_library_init. We first call a function in our bindings library that creates an initialization object. This object registers the initialization and termination functions of the GDExtension. Furthermore, it sets the level of initialization (core, servers, scene, editor, level).

At last, we need the header file for the register_types.cpp named register_types.h.

  1. #ifndef GDEXAMPLE_REGISTER_TYPES_H
  2. #define GDEXAMPLE_REGISTER_TYPES_H
  4. #include <godot_cpp/core/class_db.hpp>
  6. using namespace godot;
  8. void initialize_example_module(ModuleInitializationLevel p_level);
  9. void uninitialize_example_module(ModuleInitializationLevel p_level);
  11. #endif // GDEXAMPLE_REGISTER_TYPES_H

Compiling the plugin

We cannot easily write by hand a SConstruct file that SCons would use for building. For the purpose of this example, just use this hardcoded SConstruct file we’ve prepared. We’ll cover a more customizable, detailed example on how to use these build files in a subsequent tutorial.

Note

This SConstruct file was written to be used with the latest godot-cpp master, you may need to make small changes using it with older versions or refer to the SConstruct file in the Godot 4.0 documentation.

Once you’ve downloaded the SConstruct file, place it in your GDExtension folder structure alongside godot-cpp, src and demo, then run:

  1. scons platform=<platform>

You should now be able to find the module in demo/bin/<platform>.

Note

Here, we’ve compiled both godot-cpp and our gdexample library as debug builds. For optimized builds, you should compile them using the target=template_release switch.

Using the GDExtension module

Before we jump back into Godot, we need to create one more file in demo/bin/.

This file lets Godot know what dynamic libraries should be loaded for each platform and the entry function for the module. It is called gdexample.gdextension.

  1. [configuration]
  3. entry_symbol = "example_library_init"
  4. compatibility_minimum = "4.1"
  6. [libraries]
  8. macos.debug = "res://bin/libgdexample.macos.template_debug.framework"
  9. macos.release = "res://bin/libgdexample.macos.template_release.framework"
  10. windows.debug.x86_32 = "res://bin/libgdexample.windows.template_debug.x86_32.dll"
  11. windows.release.x86_32 = "res://bin/libgdexample.windows.template_release.x86_32.dll"
  12. windows.debug.x86_64 = "res://bin/libgdexample.windows.template_debug.x86_64.dll"
  13. windows.release.x86_64 = "res://bin/libgdexample.windows.template_release.x86_64.dll"
  14. linux.debug.x86_64 = "res://bin/libgdexample.linux.template_debug.x86_64.so"
  15. linux.release.x86_64 = "res://bin/libgdexample.linux.template_release.x86_64.so"
  16. linux.debug.arm64 = "res://bin/libgdexample.linux.template_debug.arm64.so"
  17. linux.release.arm64 = "res://bin/libgdexample.linux.template_release.arm64.so"
  18. linux.debug.rv64 = "res://bin/libgdexample.linux.template_debug.rv64.so"
  19. linux.release.rv64 = "res://bin/libgdexample.linux.template_release.rv64.so"
  20. android.debug.x86_64 = "res://bin/libgdexample.android.template_debug.x86_64.so"
  21. android.release.x86_64 = "res://bin/libgdexample.android.template_release.x86_64.so"
  22. android.debug.arm64 = "res://bin/libgdexample.android.template_debug.arm64.so"
  23. android.release.arm64 = "res://bin/libgdexample.android.template_release.arm64.so"

This file contains a configuration section that controls the entry function of the module. You should also set the minimum compatible Godot version with compatability_minimum, which prevents older version of Godot from trying to load your extension.

The libraries section is the important bit: it tells Godot the location of the dynamic library in the project’s filesystem for each supported platform. It will also result in just that file being exported when you export the project, which means the data pack won’t contain libraries that are incompatible with the target platform.

Finally, the dependencies section allows you to name additional dynamic libraries that should be included as well. This is important when your GDExtension plugin implements someone else’s library and requires you to supply a third-party dynamic library with your project.

Here is another overview to check the correct file structure:

  1. gdextension_cpp_example/
  2. |
  3. +--demo/                  # game example/demo to test the extension
  4. |   |
  5. |   +--main.tscn
  6. |   |
  7. |   +--bin/
  8. |       |
  9. |       +--gdexample.gdextension
  10. |
  11. +--godot-cpp/             # C++ bindings
  12. |
  13. +--src/                   # source code of the extension we are building
  14. |   |
  15. |   +--register_types.cpp
  16. |   +--register_types.h
  17. |   +--gdexample.cpp
  18. |   +--gdexample.h

Time to jump back into Godot. We load up the main scene we created way back in the beginning and now add a newly available GDExample node to the scene:

../../../_images/gdextension_cpp_nodes.webp

We’re going to assign the Godot logo to this node as our texture, disable the centered property:

../../../_images/gdextension_cpp_sprite.webp

We’re finally ready to run the project:

../../../_images/gdextension_cpp_animated.gif

Custom editor icon

By default, Godot uses the node icon in the scene dock for GDExtension nodes. The custom icon can be added via the gdextension file. The node’s icon is set by reference to its name and resource path of an SVG file.

For example:

  1. [icons]
  3. GDExample = "res://icons/gd_example.svg"

The path should point to a 16 by 16 pixel SVG image. Read the guide for creating icons for more information.

Adding properties

GDScript allows you to add properties to your script using the export keyword. In GDExtension you have to register the properties with a getter and setter function or directly implement the _get_property_list, _get and _set methods of an object (but that goes far beyond the scope of this tutorial).

Lets add a property that allows us to control the amplitude of our wave.

In our gdexample.h file we need to add a member variable and getter and setter functions:

  1. ...
  2. private:
  3.     double time_passed;
  4.     double amplitude;
  6. public:
  7.     void set_amplitude(const double p_amplitude);
  8.     double get_amplitude() const;
  9. ...

In our gdexample.cpp file we need to make a number of changes, we will only show the methods we end up changing, don’t remove the lines we’re omitting:

  1. void GDExample::_bind_methods() {
  2.     ClassDB::bind_method(D_METHOD("get_amplitude"), &GDExample::get_amplitude);
  3.     ClassDB::bind_method(D_METHOD("set_amplitude", "p_amplitude"), &GDExample::set_amplitude);
  4.     ClassDB::add_property("GDExample", PropertyInfo(Variant::FLOAT, "amplitude"), "set_amplitude", "get_amplitude");
  5. }
  7. GDExample::GDExample() {
  8.     // Initialize any variables here.
  9.     time_passed = 0.0;
  10.     amplitude = 10.0;
  11. }
  13. void GDExample::_process(double delta) {
  14.     time_passed += delta;
  16.     Vector2 new_position = Vector2(
  17.         amplitude + (amplitude * sin(time_passed * 2.0)),
  18.         amplitude + (amplitude * cos(time_passed * 1.5))
  19.     );
  21.     set_position(new_position);
  22. }
  24. void GDExample::set_amplitude(const double p_amplitude) {
  25.     amplitude = p_amplitude;
  26. }
  28. double GDExample::get_amplitude() const {
  29.     return amplitude;
  30. }

Once you compile the module with these changes in place, you will see that a property has been added to our interface. You can now change this property and when you run your project, you will see that our Godot icon travels along a larger figure.

Let’s do the same but for the speed of our animation and use a setter and getter function. Our gdexample.h header file again only needs a few more lines of code:

  1. ...
  2.     double amplitude;
  3.     double speed;
  4. ...
  5.     void _process(double delta) override;
  6.     void set_speed(const double p_speed);
  7.     double get_speed() const;
  8. ...

This requires a few more changes to our gdexample.cpp file, again we’re only showing the methods that have changed so don’t remove anything we’re omitting:

  1. void GDExample::_bind_methods() {
  2.     ...
  3.     ClassDB::bind_method(D_METHOD("get_speed"), &GDExample::get_speed);
  4.     ClassDB::bind_method(D_METHOD("set_speed", "p_speed"), &GDExample::set_speed);
  5.     ClassDB::add_property("GDExample", PropertyInfo(Variant::FLOAT, "speed", PROPERTY_HINT_RANGE, "0,20,0.01"), "set_speed", "get_speed");
  6. }
  8. GDExample::GDExample() {
  9.     time_passed = 0.0;
  10.     amplitude = 10.0;
  11.     speed = 1.0;
  12. }
  14. void GDExample::_process(double delta) {
  15.     time_passed += speed * delta;
  17.     Vector2 new_position = Vector2(
  18.         amplitude + (amplitude * sin(time_passed * 2.0)),
  19.         amplitude + (amplitude * cos(time_passed * 1.5))
  20.     );
  22.     set_position(new_position);
  23. }
  25. ...
  27. void GDExample::set_speed(const double p_speed) {
  28.     speed = p_speed;
  29. }
  31. double GDExample::get_speed() const {
  32.     return speed;
  33. }

Now when the project is compiled, we’ll see another property called speed. Changing its value will make the animation go faster or slower. Furthermore, we added a property range which describes in which range the value can be. The first two arguments are the minimum and maximum value and the third is the step size.

Note

For simplicity, we’ve only used the hint_range of the property method. There are a lot more options to choose from. These can be used to further configure how properties are displayed and set on the Godot side.

Signals

Last but not least, signals fully work in GDExtension as well. Having your extension react to a signal given out by another object requires you to call connect on that object. We can’t think of a good example for our wobbling Godot icon, we would need to showcase a far more complete example.

This is the required syntax:

  1. some_other_node->connect("the_signal", Callable(this, "my_method"));

To connect our signal the_signal from some other node with our method my_method, we need to provide the connect method with the name of the signal and a Callable. The Callable holds information about an object on which a method can be called. In our case, it associates our current object instance this with the method my_method of the object. Then the connect method will add this to the observers of the_signal. Whenever the_signal is now emitted, Godot knows which method of which object it needs to call.

Note that you can only call my_method if you’ve previously registered it in your _bind_methods method. Otherwise Godot will not know about the existence of my_method.

To learn more about Callable, check out the class reference here: Callable.

Having your object sending out signals is more common. For our wobbling Godot icon, we’ll do something silly just to show how it works. We’re going to emit a signal every time a second has passed and pass the new location along.

In our gdexample.h header file, we need to define a new member time_emit:

  1. ...
  2.     double time_passed;
  3.     double time_emit;
  4.     double amplitude;
  5. ...

This time, the changes in gdexample.cpp are more elaborate. First, you’ll need to set time_emit = 0.0; in either our _init method or in our constructor. We’ll look at the other 2 needed changes one by one.

In our _bind_methods method, we need to declare our signal. This is done as follows:

  1. void GDExample::_bind_methods() {
  2.     ...
  3.     ClassDB::add_property("GDExample", PropertyInfo(Variant::FLOAT, "speed", PROPERTY_HINT_RANGE, "0,20,0.01"), "set_speed", "get_speed");
  5.     ADD_SIGNAL(MethodInfo("position_changed", PropertyInfo(Variant::OBJECT, "node"), PropertyInfo(Variant::VECTOR2, "new_pos")));
  6. }

Here, our ADD_SIGNAL macro can be a single call with a MethodInfo argument. MethodInfo‘s first parameter will be the signal’s name, and its remaining parameters are PropertyInfo types which describe the essentials of each of the method’s parameters. PropertyInfo parameters are defined with the data type of the parameter, and then the name that the parameter will have by default.

So here, we add a signal, with a MethodInfo which names the signal “position_changed”. The PropertyInfo parameters describe two essential arguments, one of type Object, the other of type Vector2, respectively named “node” and “new_pos”.

Next, we’ll need to change our _process method:

  1. void GDExample::_process(double delta) {
  2.     time_passed += speed * delta;
  4.     Vector2 new_position = Vector2(
  5.         amplitude + (amplitude * sin(time_passed * 2.0)),
  6.         amplitude + (amplitude * cos(time_passed * 1.5))
  7.     );
  9.     set_position(new_position);
  11.     time_emit += delta;
  12.     if (time_emit > 1.0) {
  13.         emit_signal("position_changed", this, new_position);
  15.         time_emit = 0.0;
  16.     }
  17. }

After a second has passed, we emit our signal and reset our counter. We can add our parameter values directly to emit_signal.

Once the GDExtension library is compiled, we can go into Godot and select our sprite node. In the Node dock, we can find our new signal and link it up by pressing the Connect button or double-clicking the signal. We’ve added a script on our main node and implemented our signal like this:

  1. extends Node
  3. func _on_Sprite2D_position_changed(node, new_pos):
  4.     print("The position of " + node.get_class() + " is now " + str(new_pos))

Every second, we output our position to the console.

Next steps

We hope the above example showed you the basics. You can build upon this example to create full-fledged scripts to control nodes in Godot using C++.

Previous Next

© Copyright 2014-present Juan Linietsky, Ariel Manzur and the Godot community (CC BY 3.0). Revision 53e837c6.

Built with Sphinx using a theme provided by Read the Docs.