[issue] OperaGX native extension WASM

Padouk

Member
Anyone made it to OperaGX native extension yet - More specifically a WASM?
--

I'm trying to port one of my working HTML5 extension using JS+WASM typical combo

Using the Web export, it's working fine (see screenshot) the JS has responsability for loading the WASM in due time.
--
Using the OperaGX export the build fails to load. There's automagic attempt at loading any WASM in the project regardless of the JS and it fails with the following error:
Code:
runner.html:250 To use dlopen, you need to use Emscripten's linking support, see https://github.com/emscripten-core/emscripten/wiki/Linking
printErr @ runner.html:250
runner.js:25 Uncaught RuntimeError: abort(To use dlopen, you need to use Emscripten's linking support, see https://github.com/emscripten-core/emscripten/wiki/Linking). Build with -s ASSERTIONS=1 for more info.
    at E (runner.js:25)
    at Wb (runner.js:299)
    at runner.wasm
    at runner.wasm
    at runner.wasm
    at runner.wasm
    at runner.wasm
    at Qj.b.<computed> (runner.js:283)
    at z.dynCall_idi (runner.js:382)
    at c (runner.js:341)
I definitivly don't try (nor need to) dynamic link my wasm to anything... I'm not sure yet if i'm missing some linking attributs to forbid it when using emcc, if I'm missing some binding attributes or if the runner.wasm was simply not build with proper support there and i'm screwed.

Here's the simplest project I could think of if anyone with emcc experience cares to share some insights https://www.padouk.ca/gmsforum/ext_simple_emscript.zip.
It was built using Emscripten 2.0.1
 

Attachments

Top