Building wasm32 without wasm-bindgen #8641
Unanswered
anderspitman
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Depending on the symbols in question, perhaps we can make their dependency optional. Could it be that those are console related? Perhaps you could try building without std? The software renderer should still work in such an environment. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Been loving working with Slint. Awesome product.
I'm working on porting Slint to a custom WASM runtime. The runtime only provides the most basic functionality like providing event inputs and output via a framebuffer.
I tried building my app with
--target wasm32-unknown-unknown
. It builds (after settingdefault-features = false, features = ["compat-1-2", "std"]
), but fails to run because it's expecting a bunch of wasm-bindgen imports that don't exist in my runtime.Is there a way to build Slint for wasm without using wasm-bindgen, or are they tightly coupled?
I tried building for
wasm32-wasip1
and that resulting in a lot fewer imports, which I might be able to stub out, but I'd prefer to get it working completely freestanding.Beta Was this translation helpful? Give feedback.
All reactions