You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
warning: error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-unknown"'
warning: 1 error generated.
error: failed to run custom build command for `ring v0.17.5`
That in turn is depended on by rustls 0.21.8 and rustls-webpki 0.101.7, and sct 0.7.1, which come in through ureq, which is a dependency in our scenes crate to support the download feature.
I posted #392 yesterday, but I'm now thinking the proper fix is to remove the ureq dependency on wasm.
The text was updated successfully, but these errors were encountered:
The download feature caused CI failures on wasm, due to dependencies breaking in ways difficult to diagnose. I searched the issues for the relevant dependencies and didn't find other people running into the same problem.
Since I worry that these deps may continue to be unstable, I think the best thing is to disable them on wasm builds. This shouldn't affect any functionality we actually care about.
Longer term, we probably want to move these more sophisticated examples out of the vello crate proper.
Fixes#394
This command is failing and can be replicated locally after
cargo update
:RUSTFLAGS=--cfg=web_sys_unstable_apis cargo check -p with_winit --target wasm32-unknown-unknown
The error is in the compilation of ring 0.17.5
That in turn is depended on by rustls 0.21.8 and rustls-webpki 0.101.7, and sct 0.7.1, which come in through ureq, which is a dependency in our
scenes
crate to support the download feature.I posted #392 yesterday, but I'm now thinking the proper fix is to remove the ureq dependency on wasm.
The text was updated successfully, but these errors were encountered: