Sam Clegg
Sam Clegg
See https://github.com/emscripten-core/emscripten/pull/25439
I think we should only consider keeping it around if there are active users of the feature. If there are none, I don't see any point in maintaining it and...
I performed the following global github search: https://github.com/search?q=%2F%28%3F-i%29%5CbsPROXY_TO_WORKER%5Cb%2F+-org%3Aemscripten-core+-path%3Aemcc.*+-path%3Asettings.*+-path%3Asettings_reference.*+-path%3Acommon.py+-path%3Ashell.js+-path%3A*wasm_worker*&type=code&p=5 None of the result, as far as I can tell, were actual live usages of the setting.
For the `--proxy-to-worker` flags that where more hits, but its hard for me to tell if any of them actually live usages: https://github.com/search?q=%2F%28%3F-i%29%5Cbproxy-to-worker%5Cb%2F+-org%3Aemscripten-core+-path%3Aemcc.*+-path%3Asettings.*+-path%3Asettings_reference.*+-path%3Acommon.py+-path%3Ashell.js+-path%3A*wasm_worker*&type=code
As for internal usage withing google I found non at all.
Hi @MuTsunTsai, thanks for letting us know. Please let us know hard it is is for you to move to different solution. If you its not possible, and you need...
Sorry , my mistake.
No, not too late.
Side modules are actually just `.wasm` files so I would recommend using `.wasm` or just leave them as `.so`. Is there some reason why `.so` doesn't work for you?
I mean, technically it is a shared library, just one that contains wasm bits. `.so` files for different architectures, or even different executable file formats are still called `.so`. With...