-
Notifications
You must be signed in to change notification settings - Fork 6
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
WASM support #27
Comments
Wow, interesting idea. I don't know much about WASM, either. But my preferred approach would be your second suggestion: a separate crate to generate the WASM blob. |
Most rust-wasm packages use the |
I'm going to close this issue because nobody seems to be working on it. And to be clear, I'm not going to do it myself; I know nothing about wasm or browsers. But I can help you with the blosc side if you try it. |
In case anyone comes here to try this, there's currently some work to make the C - Rust wasm story a lot simpler: rustwasm/wasm-bindgen#3454 |
By linking a C library, it's obviously harder to get blosc-rs to run in a browser. However, c-blosc itself can be compiled to WASM (see Blosc/c-blosc#238 (comment) and https://github.com/manzt/numcodecs.js/tree/main/codecs/blosc ). I don't know much about linking C libraries or WASM itself (other than running
cargo build
and praying...); is it possible to bake that kind of configuration into abuild.rs
and gain WASM support for blosc-sys? I gather the hard bit is the FFI between rust and C.I suppose there could alternatively be a separate crate which generates a WASM blob as above and then writes a dependent rust wrapper around it with js_sys for API niceness.
The text was updated successfully, but these errors were encountered: