Godot 3.5: Internet Construct utilizing customized GDNative C++ Library doesn’t work because of `dlopen` error and failed linking

The Drawback

At the moment I’m attempting to get the official GDNative C++ instance for Godot 3.5, which may be discovered right here working within the Internet Export context. Up to now, I managed to export to X11.64 with none troubles and managed to arrange the creation pipeline for the Internet Meeting (see part “Internet Meeting Creation Course of” beneath), which now produces a legitimate output with none error messages. Nevertheless, as quickly as I attempt to run the sport in any browser, it stops loading and shows the next error message:

Aborted(To make use of dlopen, you want allow dynamic linking, 
see https://github.com/emscripten-core/emscripten/wiki/Linking)

This hyperlink solely accommodates a hyperlink to the brand new documentation of emscripten, which is used to create the Internet Meeting file, and is on the time of writing positioned at https://emscripten.org/docs/compiling/Dynamic-Linking.html.

Last File Construction

ROOT/
  ├─godot-project-src/
  |   └─lib/
  |      ├─wasm/
  |      |   └─libsimple.wasm
  |      ├─SimpleLibrary.gdnlib
  |      └─SimpleLibrary.gdns
  └─SimpleLibrary/
      ├─godot-cpp/
      |    ├─bin/
      |    |  └─libgodot-cpp.javascript.launch.wasm.a
      |    ├─embody/
      |    |   ├─core/
      |    |   └─gen/
      |    └─godot-headers/
      ├─bin/
      |  └─libsimple.wasm
      └─src/
         └─init.cpp

Internet Meeting Creation and Export Course of

At the start of the challenge (solely crucial as soon as):

1. Initialize SimpleLibrary listing with godot-cpp and godot-headers.
2. Create the discharge JavaScript Godot Binding by way of
   scons platform=javascript generate_bindings=sure goal=launch,
   which creates the archive SimpleLibrary/godot-cpp/bin/libgodot-cpp.javascript.launch.wasm.a.
3. Create GDNative Import Recordsdata within the Godot Challenge Listing.

    godot-project-src/lib/SimpleLibrary.gdnlib
    godot-project-src/lib/SimpleLibrary.gdns
   

After every change:

1. Create the brand new Internet Meeting Library

    cd SimpleLibrary
    emcc -o bin/libsimple.wasm -g -O3 -sSIDE_MODULE=1 src/init.cpp godot-cpp/bin/libgodot-cpp.javascript.launch.wasm.a -Igodot-cpp/embody -Igodot-cpp/embody/core -Igodot-cpp/embody/gen -Igodot-cpp/godot-headers
   

2. Copy the newly created library to the right location within the Godot Challenge Folder

   cp bin/libsimple.wasm ../godot-project-src/lib/wasm

3. Replace (if crucial) the GDNative Import Recordsdata within the Godot Challenge Listing.

    godot-project-src/lib/SimpleLibrary.gdnlib
    godot-project-src/lib/SimpleLibrary.gdns
   

Internet Export

Simply choosing the HTML Export Template by way of the Godot Editor, selecting the Export Folder and let Godot do its factor.

Questions

1. Did I miss some crucial settings throughout the Internet Meeting creation? I already needed to change some compiler flags for emccand add embody directories in comparison with the unique instance to get it even to compile. I additionally experimented with the optimization flags, the deprecated -shared flag, -sDYNAMIC_EXECUTION, -sMAIN_MODULE, however no modifications.
2. Do I’ve to create a customized HTML Export Template for this to work correctly? In line with the GDNative Documentation, if

   godot-project-src/lib/SimpleLibrary.gdnlib
   godot-project-src/lib/SimpleLibrary.gdns

are created correctly, this shouldn’t be crucial.

3. Is the GDNative C++ Internet Export in any respect doable? Throughout my analysis, I solely discovered very imprecise documentation, a number of (not likely associated) github points and extra questions than solutions.