You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of messing around with godot export templates or emscripten in
order to either:
1. dlopen the gdextension lib with global flag (which may come with
unforeseen problems from broadly exposing miscellaneous new symbols
from the dso).
2. Reconsider the lookup scope of `dynCall_<sig>` in the generated
`invoke_<sig>` methods (i.e. when an invoke_<sig> is generated,
also make it remember the originating dso and fall back to lookup
in the dso exports if the `dynCall` is not found globally)
I instead opt to simply promote the selected troublesome symbols from
the dso to Module scope as early as possible at the gdextension entry
point, whilst also searching for and executing the constructor methods
which set up state for the subsequent class registrations.
-----------
Tested With:
Godot Engine v4.1.3.stable.official [f06b6836a]
(default export templates, dlink variant)
rustc 1.75.0-nightly (2f1bd0729 2023-10-27)
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.47 (431685f05c67f0424c11473cc16798b9587bb536)
Chrome Version 120.0.6093.0 (Official Build) canary (arm64)
0 commit comments