working around dyncall issues

[ricomariani]

I ran into this issue:

https://github.com/emscripten-core/emscripten/pull/13883/commits

I was able to workaround with some minor changes in the Makefile:

dist/wa-sqlite.mjs: $(BITCODE_FILES) $(LIBRARY_FILES) $(EXPORTED_FUNCTIONS) $(EXTRA_EXPORTED_RUNTIME_METHODS)
        mkdir -p dist
        EMCC_CLOSURE_ARGS="--externs my_externs.js" $(EMCC) $(EMFLAGS) $(EMFLAGS_DIST) \
          $(EMFLAGS_INTERFACES) \
          $(EMFLAGS_LIBRARIES) \
          $(BITCODE_FILES) -o $@

dist/wa-sqlite-async.mjs: $(BITCODE_FILES) $(LIBRARY_FILES) $(EXPORTED_FUNCTIONS) $(EXTRA_EXPORTED_RUNTIME_METHODS) $(ASYNCIFY_IMPORTS)
        mkdir -p dist
        EMCC_CLOSURE_ARGS="--externs my_externs.js" $(EMCC) $(EMFLAGS) $(EMFLAGS_DIST) \
          $(EMFLAGS_INTERFACES) \
          $(EMFLAGS_LIBRARIES) \
          $(EMFLAGS_ASYNCIFY_DIST) \
          $(BITCODE_FILES) -o $@

And this tiny side file:

-- my_externs.js
// @externs
var dynCall_v;

[rhashimoto]

Yes, I'm the one who filed this bug with Emscripten and it's mentioned in the README:

Note that there is a regression in EMSDK 2.0.14 that prevents building.

In the bug I suggest exactly this workaround. 😀

[ricomariani]

Ha, I didn't notice it was you :D

I had no trouble tweaking the Makefile.