-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
wgpu-hal causes resolver error #3205
Comments
Does the error persist when you add resolver="2" to your package/workspace properties (which is suggested in the error message)? |
Where am I supposed to add that? I tried putting it in the cargo.toml but the problem persisted |
you should add it here https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions alternatively, if you are on latest rust, you can use edition 2021 which will select it by default |
Cheers @mockersf, 2021 did the trick. I was using 2018 still for some reason lol |
I think we should work with the wgpu team to provide more actionable guidance there. Hopefully compile_error can accept a multiline string. |
Agreed, that error message doesn't really point you to a solution. I did my usual google run and found nothing. Only thing I found was this https://doc.rust-lang.org/cargo/reference/resolver.html and it doesn't even show you how to change the resolver I take that back I just didn't read far enough haha |
Cheers @alice-i-cecile XD |
Just a note for those new to Rust like me that if your packages are in a workspace, you need to indicate the resolver in the workspace's Cargo.toml file also. But in the workspace's Cargo.toml, it has to be " |
404s for me now. Direct link: rust-lang/cargo#9956 |
Bevy version
main
branch, commit: e8412dfOperating system & version
Arch Linux fully up to date
What you did
cargo run
What you expected to happen
Runs correctly
What actually happened
Additional information
I saw #2712 but I'm completely up to date so I don't know what else to do.
The text was updated successfully, but these errors were encountered: