-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
There are plans to support wasm? #205
Comments
I think it's already supported? |
|
You need to use emscripten target, which provides stdio.h and alike. rustup target add wasm32-unknown-emscripten
# install emscripten and set up env for emcc, and then
cargo build --target wasm32-unknown-emscripten --lib |
rust-lang/rust#85821 this。reslove my error |
Great. |
Do you have the glue js for the wasm project? I found that the wasm file packaged in the project is difficult to use |
No, I don't. You'll have to use the public interface in Rust, and then export (perhaps with wasm-bindgen) your own entry point. |
wasm-bindge is use wasm32-unknown-unknown? but gifski is only use wasm32-unknown-emscripten |
Ooof, indeed. You'll need to manually write the wrapper using |
I have given up using wasm, on the server,How to start multithreading, currently only two CPUs are used |
No description provided.
The text was updated successfully, but these errors were encountered: