Sam Clegg
Sam Clegg
The `emscripten::function` calls need to be placed inside and EMSCRIPTEN_BINDINGS block. In your small example I don't see that so wanted to check that you are indeed doing that.
CC @littledan who added the wording about these union types.
Closing this since we have gone ahead with this change now on the wasm side.
Once this lands I think we can add some tests to the emscripten CI (Following up on https://github.com/emscripten-core/emscripten/pull/22964).
The wasm file you are trying to load has had its import names minified as part of code size optimization. That is why the import its looking for is `a.X`...
When you build a wasm file with emscripten it also produces a js file. In your case it looks like that file is called web-ifc-api.js. If you didn't build that...
I can think of a couple of options you might want to try: 1. Write a small post-link tool that simply checks the export list and throws an error. 2....
The WASI APIs that are part of `wasi_snapshot_preview1` are not part of the web platform, so if you want to run a WASI program on the web you would need...
Pretty much any WASI program (i.e. any program build with wasi-sdk) will depend on one or more WASI APIs. In theory could could try to build a pure compute module...