Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to turn off wasm-exceptions not available for emscripten builds #401

Closed
dsamo opened this issue Jul 5, 2024 · 2 comments · Fixed by #402
Closed

Option to turn off wasm-exceptions not available for emscripten builds #401

dsamo opened this issue Jul 5, 2024 · 2 comments · Fixed by #402

Comments

@dsamo
Copy link

dsamo commented Jul 5, 2024

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?

@Kojoley
Copy link
Contributor

Kojoley commented Jul 6, 2024

exception-handling-method=js to build with js exceptions implementation instead of wasm exceptions.
exception-handling=off to turn off exceptions entirely.

@dsamo
Copy link
Author

dsamo commented Jul 24, 2024

exception-handling-method=js to build with js exceptions implementation instead of wasm exceptions.

exception-handling=off to turn off exceptions entirely.

My jam file knowledge failed me here. Verified this works. Thanks!

@dsamo dsamo closed this as completed Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants