Closed rybertm closed 3 years ago
Looks like https://github.com/gfx-rs/wgpu-rs/blob/78234dd12030c2c4e7247d8ae1a6df08e299e44d/Cargo.toml#L23 broke the "vulkan-portability" feature on MacOS for the same reason stated above, quoted from the original issue.
The same fix could be applied unless there's other plans.
I'm thinking that, since gfx_select!
isn't ever used internally by wgpu-core
, the feature it should be checking should be "vulkan-portability" (instead of "gfx-backend-vulkan"), even though wgpu-core
doesn't have this feature.
Not sure if i should submit a PR with that change or if you want some discussion around it or ideas
A PR would be appreciated!
On Apr 5, 2021, at 18:24, Robert Broketa @.***> wrote:
Not sure if i should submit a PR with that change or if you want some discussion around it or ideas
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
I decided to remove support for Vulkan Portability, at least for the 0.8 release. The reason for it being - our validation is very good now, and Naga's Metal output is great. So we have very little value to extract from running with Vulkan Validation Layers at this point.
https://github.com/gfx-rs/wgpu-rs/blob/55cafa398868998d1c14620111208d92f5cda9d5/Cargo.toml#L23 sets the
gfx-backend-vulkan
feature insidewgpu/wgpu-core
but in this crate onlyvulkan-portability
gets set, so whengfx_select!
is expanded it checks forgfx-backend-vulkan
, which is not present inwgpu-rs
: https://github.com/gfx-rs/wgpu-rs/blob/55cafa398868998d1c14620111208d92f5cda9d5/src/backend/direct.rs#L593-L595As for fixing, I could add a
gfx-backend-vulkan
dependency to thevulkan-portability
feature as well as add it to macos targets, but I don't know if it could break in other unix systems @kvark.Originally posted by @rybertm in https://github.com/gfx-rs/wgpu-rs/issues/575#issuecomment-696066934