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
Hello, in our company we use boost builds in a webassembly client using emscripten.
Since boost 1.85 it seems by looking into the emscripten jam file that there is no way to turn off wasm-exceptions unless we use node < 16 or emscripten major version < 2.
Currently our wasm client is still using js exceptions and if we are to transition we need to put time there to investigate certain things. But with the restriction above we now have a client being built with js exceptions and a library (boost) being built with wasm-exceptions which leads to undefined symbols linker error for __wasm_lpad_context.
Is there a feature flag to build with js-exceptions explicitly?
The text was updated successfully, but these errors were encountered:
exception-handling-method=js to build with js exceptions implementation instead of wasm exceptions. exception-handling=off to turn off exceptions entirely.
Hello, in our company we use boost builds in a webassembly client using emscripten.
Since boost 1.85 it seems by looking into the emscripten jam file that there is no way to turn off wasm-exceptions unless we use node < 16 or emscripten major version < 2.
Currently our wasm client is still using js exceptions and if we are to transition we need to put time there to investigate certain things. But with the restriction above we now have a client being built with js exceptions and a library (boost) being built with wasm-exceptions which leads to undefined symbols linker error for __wasm_lpad_context.
Is there a feature flag to build with js-exceptions explicitly?
The text was updated successfully, but these errors were encountered: