C++ bindings for the Godot script API
 
 
 
 
 
 
Go to file
Rémi Verschelde 20a17eb71d
Merge pull request #748 from Faless/build/4.x_deps
2022-05-03 11:56:30 +02:00
.github [CI] Add python file format to static checks. 2022-05-02 21:13:56 +02:00
godot-headers headers: Sync with upstream commit 3e9ead0 (4.0-alpha7) 2022-04-29 19:57:26 +02:00
include/godot_cpp Color: Rename to_srgb/to_linear to include base color space 2022-04-13 12:50:21 +02:00
misc Sync `misc/` scripts and hooks with upstream Godot 2022-03-15 10:18:33 +01:00
src Update copyright year 2022-03-15 10:17:53 +01:00
test Add support for variadic method binds with the typed return. Sync headers. 2022-03-30 15:11:28 +03:00
.clang-format Update clang-format to version 11 2021-02-28 16:57:34 -03:00
.gitattributes Getting this to compile on mac os x 2017-06-16 23:50:48 +10:00
.gitignore Add `.gitignore` for test, ignore potential log files 2021-11-04 15:42:27 +01:00
.gitmodules Remove godot-headers submodule, copy files directly 2022-03-15 10:19:07 +01:00
CMakeLists.txt Sync `misc/` scripts and hooks with upstream Godot 2022-03-15 10:18:33 +01:00
LICENSE.md Update copyright year 2022-03-15 10:17:53 +01:00
Makefile Replace bindgins to work with extensions 2021-09-27 23:08:08 +10:00
README.md Update README file for macos support 2022-01-29 17:03:35 +01:00
SConstruct [Scons] Use builder to track bindings regeneration. 2022-05-03 10:48:23 +02:00
binding_generator.py [Scons] Use builder to track bindings regeneration. 2022-05-03 10:48:23 +02:00

README.md

godot-cpp

This repository contains the C++ bindings for the Godot Engine's GDExtensions API.

Versioning

This repositories follows the same branch versioning as the main Godot Engine repository:

  • master tracks the current development branch.
  • 3.x tracks the development of the next 3.x minor release.
  • Other versioned branches (e.g. 3.3, 3.2) track the latest stable release in the corresponding branch.

Stable releases are also tagged on this repository: Tags.

For any project built against a stable release of Godot, we recommend using this repository as a Git submodule, checking out the specific tag matching your Godot version.

As the master and 3.x branches are constantly getting updates, if you are using godot-cpp against a more current version of Godot, see the instructions in godot-headers for updating the relevant files.

Contributing

We greatly appreciate help in maintaining and extending this project. If you wish to help out, ensure you have an account on GitHub and create a "fork" of this repository. Rémi "Akien" Verschelde wrote an excellent bit of documentation for the main Godot project on this: Pull request workflow

Please install clang-format and copy the files in misc/hooks into .git/hooks so formatting is done before your changes are submitted.

Getting Started

It's a bit similar to what it was for 3.x but also a bit different. This new approach is much more akin to how core Godot modules are structured.

Compiling this repository generates a static library to be linked with your shared lib, just like before.

To use the shared lib in your Godot project you'll need a .gdextension file, which replaces what was the .gdnlib before. Follow the example:

[configuration]

entry_symbol = "example_library_init"

[libraries]

linux.64.debug = "bin/libgdexample.linux.debug.64.so"
linux.64.release = "bin/libgdexample.linux.release.64.so"
windows.64.debug = "bin/libgdexample.windows.debug.64.dll"
windows.64.release = "bin/libgdexample.windows.release.64.dll"
macos.debug = "bin/libgdexample.debug.framework"
macos.release = "bin/libgdexample.release.framework"

The entry_symbol is the name of the function that initializes your library. It should be similar to following layout:

extern "C" {

// Initialization.

GDNativeBool GDN_EXPORT example_library_init(const GDNativeInterface *p_interface, const GDNativeExtensionClassLibraryPtr p_library, GDNativeInitialization *r_initialization) {
	godot::GDExtensionBinding::InitObject init_obj(p_interface, p_library, r_initialization);

	init_obj.register_scene_initializer(register_example_types);
	init_obj.register_scene_terminator(unregister_example_types);

	return init_obj.init();
}
}

The register_example_types() should register the classes in ClassDB, very like a Godot module would do.

using namespace godot;
void register_example_types() {
	ClassDB::register_class<Example>();
}

Any node and resource you register will be available in the corresponding Create... dialog. Any class will be available to scripting as well.

Included Example

Check the project in the test folder for an example on how to use and register different things.