updated with suggestions

Author: paddy-exe

tutorials/scripting/gdextension/files/cpp_example/SConstruct

@@ -18,19 +18,14 @@ sources = Glob("src/*.cpp")
 
 if env["platform"] == "macos":
     library = env.SharedLibrary(
-        "demo/bin/osx/libgdexample.{}.framework".format(
-            env["platform"],
+        "demo/bin/libgdexample.{}.{}.framework/libgdexample.{}.{}".format(
+            env["platform"], env["target"], env["platform"], env["target"]
         ),
         source=sources,
     )
-elif env["platform"] == "windows":
-    library = env.SharedLibrary(
-        "demo/bin/win64/libgdexample.{}.{}{}".format(env["platform"], env["arch"], env["SHLIBSUFFIX"]),
-        source=sources,
-    )
 else:
     library = env.SharedLibrary(
-        "demo/bin/linux/libgdexample.{}.{}{}".format(env["platform"], env["arch"], env["SHLIBSUFFIX"]),
+        "demo/bin/libgdexample{}{}".format(env["suffix"], env["SHLIBSUFFIX"]),
         source=sources,
     )
 

tutorials/scripting/gdextension/gdextension_cpp_example.rst

@@ -7,7 +7,7 @@ Introduction
 ------------
 
 The C++ bindings for GDExtension are built on top of the C GDExtension API
-and provide a nicer way to "extend" nodes in Godot using C++.
+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.
 
@@ -34,14 +34,12 @@ of Godot. GDExtensions will not work in older versions of Godot (only Godot 4 an
 
 .. note::
 
-    `GDExtension <https://godotengine.org/article/introducing-gd-extensions>`__
-    has been merged in the ``master`` branch of godot-cpp,
-    but it is only compatible with the upcoming Godot 4.0.
-    Therefore, you need to use the ``master`` branch of godot-cpp to use GDExtension
-    and follow this example.
+    To use `GDExtension <https://godotengine.org/article/introducing-gd-extensions>`__
+    you need to use the ``master`` branch of godot-cpp,
+    which is only compatible with Godot 4.0 and follow this example.
 
-If you are versioning your project using Git, it is a good idea to add them as
-Git submodules:
+If you are versioning your project using Git, it is a good idea to add it as
+a Git submodule:
 
 .. code-block:: none
 
@@ -63,16 +61,11 @@ Do make sure you clone recursively to pull in both repositories:
 
     mkdir gdextension_cpp_example
     cd gdextension_cpp_example
-    git clone --recursive -b master https://github.com/godotengine/godot-cpp
+    git clone -b master https://github.com/godotengine/godot-cpp
 
 .. note::
 
-    ``godot-cpp`` now includes ``godot-headers`` as a nested submodule, if you've
-    manually downloaded them please make sure to place ``godot-headers`` inside
-    of the ``godot-cpp`` folder.
-
-    You don't have to do it this way, but we've found it easiest to manage. If you
-    decide to download the repositories or clone them into your folder,
+    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.
 
@@ -83,9 +76,9 @@ following commands:
 .. code-block:: none
 
     cd gdextension_cpp_example
-    git submodule update --init --recursive
+    git submodule update --init
 
-This will clone these two repositories into your project folder.
+This will initialize the repository in your project folder.
 
 Building the C++ bindings
 -------------------------
@@ -179,8 +172,6 @@ GDExtension node we'll be creating. We will name it ``gdexample.h``:
         GDExample();
         ~GDExample();
 
-        void _init(); // our initializer called by Godot
-
         void _process(float delta);
     };
 
@@ -208,9 +199,7 @@ 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. The third is 
-our ``_init`` function which is called after Godot has properly set up
-our object.
+as the ``_process`` function you're used to in GDScript.
 
 Let's implement our functions by creating our ``gdexample.cpp`` file:
 
@@ -222,7 +211,6 @@ Let's implement our functions by creating our ``gdexample.cpp`` file:
     using namespace godot;
 
     void GDExample::_bind_methods() {
-        ClassDB::bind_method(D_METHOD("_process"), &GDExample::_process);
     }
 
     GDExample::GDExample() {
@@ -247,9 +235,6 @@ 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.
-What stands out is calling ``owner->set_position`` to call one of the built-in
-methods of our Sprite2D. This is because our class is a container
-class; ``owner`` points to the actual Sprite2D node our script relates to.
 
 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
@@ -369,9 +354,9 @@ loaded for each platform and the entry function for the module. It is called ``g
 
     [libraries]
 
-    linux.64="res://bin/linux/libgdexample.linux.64.so"
-    windows.x86_64="res://bin/win64/libgdexample.windows.x86_64.dll"
-    macos="res://bin/osx/libgdexample.macos.framework"
+    linux.64="res://bin/libgdexample.linux.64.so"
+    windows.x86_64="res://bin/libgdexample.windows.x86_64.dll"
+    macos="res://bin/libgdexample.macos.framework"
 
 This file contains a ``configuration`` section that controls the entry function of the module.
 
@@ -428,7 +413,7 @@ 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
-sett function or directly implement the ``_get_property_list``, ``_get`` 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.
 
@@ -457,7 +442,6 @@ show the methods we end up changing, don't remove the lines we're omitting:
     void GDExample::_bind_methods() {
         ClassDB::bind_method(D_METHOD("get_amplitude"), &GDExample::get_amplitude);
         ClassDB::bind_method(D_METHOD("set_amplitude", "p_amplitude"), &GDExample::set_amplitude);
-
         ClassDB::add_property("GDExample", PropertyInfo(Variant::FLOAT, "amplitude"), "set_amplitude", "get_amplitude");
     }
 
@@ -512,6 +496,7 @@ showing the methods that have changed so don't remove anything we're omitting:
 .. code-block:: C++
 
     void GDExample::_bind_methods() {
+        ...
         ClassDB::bind_method(D_METHOD("get_speed"), &GDExample::get_speed);
         ClassDB::bind_method(D_METHOD("set_speed", "p_speed"), &GDExample::set_speed);
 	    ClassDB::add_property("GDExample", PropertyInfo(Variant::FLOAT, "speed"), "set_speed", "get_speed");
@@ -535,6 +520,8 @@ showing the methods that have changed so don't remove anything we're omitting:
         set_position(new_position);
     }
 
+    ...
+
     void GDExample::set_speed(float p_speed) {
         speed = p_speed;
     }

tutorials/scripting/gdextension/what_is_gdextension.rst

@@ -14,7 +14,7 @@ at run-time. You can use it to run native code without compiling it with the eng
           :ref:`GDScript <doc_gdscript>`.
 
 Differences between GDExtension and C++ modules
---------------------------------------------
+-----------------------------------------------
 
 You can use both GDExtension and :ref:`C++ modules <doc_custom_modules_in_c++>` to
 run C or C++ code in a Godot project.
@@ -23,11 +23,11 @@ They also both allow you to integrate third-party libraries into Godot. The one
 you should choose depends on your needs.
 
 Advantages of GDExtension
-^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Unlike modules, GDExtension doesn't require compiling the engine's source code,
 making it easier to distribute your work. It gives you access to most of the API
-available to GDScript C#, allowing you to code game logic with full control
+available to GDScript and C#, allowing you to code game logic with full control
 regarding performance. It's ideal if you need high-performance code you'd like
 to distribute as an add-on in the :ref:`asset library <doc_what_is_assetlib>`.
 
@@ -54,8 +54,6 @@ GDExtension isn't enough:
   static modules
 - You can use C++ modules to provide additional features in a project without
   carrying native library files around. This extends to exported projects.
-(- C++ modules can be faster than GDExtension, especially when the code requires a
-  lot of communication through the scripting API.) -> TODO: check if this still holds up
 
 Supported languages
 -------------------
@@ -90,9 +88,6 @@ The bindings below are developed and maintained by the community:
 Version compatibility
 ---------------------
 
-(:ref:`Unlike Godot itself <doc_release_policy>`, GDExtension has stricter version
-compatibility requirements as it relies on low-level *ptrcalls* to function.) -> TODO: check up on this
-
 GDExtension add-ons compiled for a given Godot version are only guaranteed to work
 with the same minor release series. For example, a GDExtension add-on compiled for
 Godot 4.0 will only work with Godot 4.0, 4.0.1, 4.0.2. In addition, GDExtension is