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

emscrioten and wasm .. seems to expect rayon+threads #1588

Closed
dobkeratops opened this issue Oct 28, 2021 · 1 comment
Closed

emscrioten and wasm .. seems to expect rayon+threads #1588

dobkeratops opened this issue Oct 28, 2021 · 1 comment

Comments

@dobkeratops
Copy link

has this crate been used in the browser?
my project uses the image crate and is being ported to wasm32/emscrioten;

it crashes on startup reporting that threads arent available;

i can get it past that using “default-features = false” but then its not managung to decode textures (as far as i can tell)

Q1 could anyone verify if this should work
Q2 could the library default to no threading on the wasm targets

whats the thinking on this

@jbg
Copy link

jbg commented Oct 28, 2021

duplicate of #1496

You probably need to re-enable some of the features disabled by default-features = false to regain the support for decoding your textures, just don't enable the threading/rayon features.

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

No branches or pull requests

3 participants