Attention: Here be dragons
This is the latest
(unstable) version of this documentation, which may document features
not available in or compatible with released stable versions of Godot.
Checking the stable version of the documentation...
The .gdextension file¶
前言¶
The .gdextension file in your project contains the instructions for how to load
the GDExtension. The instructions are separated into specific sections. This page
should give you a quick overview of the different options available to you. For an introduction
how to get started with GDExtensions take a look at the GDExtension C++ Example.
Configuration section¶
Property |
类型 |
描述 |
|---|---|---|
entry_symbol |
字符串 |
Name of the entry function for initializing the GDExtension. This function should be defined in
the |
compatibility_minimum |
字符串 |
Minimum compatible version. This prevents older versions of Godot from loading extensions that depend on features from newer versions of Godot. Only supported in Godot 4.1 or later |
compatibility_maximum |
字符串 |
Maximum compatible version. This prevents newer versions of Godot from loading the extension. Only supported in Godot 4.3 or later |
reloadable |
Boolean |
Reloads the extension upon recompilation. Reloading is supported for the godot-cpp binding in Godot 4.2 or later. Other language bindings may or may not support it as well. This flag should be mainly used for developing or debugging an extension. |
android_aar_plugin |
Boolean |
The GDExtension is part of a v2 Android plugin. During export this flag will indicate to the editor that the GDExtension native shared libraries are exported by the Android plugin AAR binaries. |
Libraries section¶
In this section you can set the paths to the compiled binaries of your GDExtension libraries.
By specifying feature flags you can filter which version should be loaded and exported with your
game depending on which feature flags are active. Every feature flag must match to Godot's
feature flags or your custom export flags to be loaded in an exported game. For instance macos.debug
means that it will be loaded if Godot has both the macos and debug flag active. Each
line of the section is evaluated from top to bottom.
Here is an example of what that can look like:
[libraries]
macos.debug = "res://bin/libgdexample.macos.template_debug.framework"
macos.release = "res://bin/libgdexample.macos.template_release.framework"
windows.debug.x86_32 = "res://bin/libgdexample.windows.template_debug.x86_32.dll"
windows.release.x86_32 = "res://bin/libgdexample.windows.template_release.x86_32.dll"
windows.debug.x86_64 = "res://bin/libgdexample.windows.template_debug.x86_64.dll"
windows.release.x86_64 = "res://bin/libgdexample.windows.template_release.x86_64.dll"
linux.debug.x86_64 = "res://bin/libgdexample.linux.template_debug.x86_64.so"
linux.release.x86_64 = "res://bin/libgdexample.linux.template_release.x86_64.so"
linux.debug.arm64 = "res://bin/libgdexample.linux.template_debug.arm64.so"
linux.release.arm64 = "res://bin/libgdexample.linux.template_release.arm64.so"
linux.debug.rv64 = "res://bin/libgdexample.linux.template_debug.rv64.so"
linux.release.rv64 = "res://bin/libgdexample.linux.template_release.rv64.so"
Here are lists of some of the available built-in options (for more look at the feature tags):
Running system¶
Flag |
描述 |
|---|---|
windows |
Windows operating system |
macos |
Mac operating system |
linux |
Linux operating system |
bsd |
BSD operating system |
linuxbsd |
Linux or BSD operating system |
android |
Android operating system |
ios |
iOS operating system |
web |
Web browser |
Build¶
Flag |
描述 |
|---|---|
debug |
Build with debug symbols |
release |
Optimized build without debug symbols |
editor |
Editor build |
架构¶
Flag |
描述 |
|---|---|
double |
double-precision build |
single |
single-precision build |
x86_64 |
64-bit x86 build |
arm64 |
64-bit ARM build |
rv64 |
64-bit RISC-V build |
riscv |
RISC-V build (any bitness) |
wasm32 |
32-bit WebAssembly build |
Icons section¶
By default, Godot uses the Node icon in the scene dock for GDExtension nodes. A custom icon can be set by reference to its name and resource path of an SVG file.
例如:
[icons]
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.
Dependencies section¶
In this section you set the paths of the GDExtension dependencies. This is used internally to export the dependencies when exporting your game executable. You are able to set which dependency is loaded depending on the feature flags of the exported executable. In addition, you are able to set an optional subdirectory to move your dependencies into. If no path is supplied Godot will move the libraries into the same directory as your game executable.
警告
In MacOS it is necessary to have shared libraries inside a folder called Frameworks with a directory structure
like this: Game.app/Contents/Frameworks.
[dependencies]
macos.debug = {
"res://bin/libdependency.macos.template_debug.framework" : "Contents/Frameworks"
}
macos.release = {
"res://bin/libdependency.macos.template_release.framework" : "Contents/Frameworks"
}
windows.debug = {
"res://bin/libdependency.windows.template_debug.x86_64.dll" : "",
"res://bin/libdependency.windows.template_debug.x86_32.dll" : ""
}
windows.release = {
"res://bin/libdependency.windows.template_release.x86_64.dll" : "",
"res://bin/libdependency.windows.template_release.x86_32.dll" : ""
}
linux.debug = {
"res://bin/libdependency.linux.template_debug.x86_64.so" : "",
"res://bin/libdependency.linux.template_debug.arm64.so" : "",
"res://bin/libdependency.linux.template_debug.rv64.so" : ""
}
linux.release = {
"res://bin/libdependency.linux.template_release.x86_64.so" : "",
"res://bin/libdependency.linux.template_release.arm64.so" : "",
"res://bin/libdependency.linux.template_release.rv64.so" : ""
}