The Rust wasm community seems to prefer wasm32-unknown-unknown these
days. Unfortunately, my use case needs C libraries that will never be
rewritten. I have a fairly small API surface that I'm calling from Yew
(Rust front-end framework) but I'm starting to think I'd be better
served by trying to export that API surface to JS and switching the UI
to a more traditional framework. Is this site still a good reference for
how to do this?
https://hoverbear.org/2017/04/06/the-path-to-rust-on-the-web/
Specifically, it creates a C library wrapping the exported Rust
functions, then an empty `main()`. Given how fast these ecosystems move,
I was wondering if any of this work could be automated? wasm-bindgen is
for wasm32-unknown-unknown if I understand correctly, but I thought I'd
check that assumption.
Are there any current examples of someone building JS modules using Rust
and Emscripten? Or has everyone in the Rust community switched
exclusively to wasm32-unknown-unknown?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
