-
Notifications
You must be signed in to change notification settings - Fork 11
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
Replace vello's default wgpu
feature with an optional wgpu
feature
#17
Conversation
Looks like the same fix needs to be applied to |
5e0993f
to
90c3063
Compare
Can you explain why we wouldn't want the default feature for |
So that crates using |
Please update the CHANGELOG and I can merge this |
Before pushing an updated changelog: since this crate reexports |
Yeah, let's do that. |
90c3063
to
a9f2971
Compare
@simbleau done. |
vello
to remove wgpu
wgpu
feature with an optional vello-wgpu
feature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's change that feature name to just wgpu
.
…ature linebender/vello#359 made `wgpu` an optional but default dependency/feature, but any crate using `velato` will be forced to opt in to `wgpu` due to not disabling the default here. Since `velato` does not need any rendering backend at all, this feature should be disabled by default. As the `vello` crate is reexported from the root, a `wgpu` passthrough feature is provided so that users can turn it back on without explicitly depending on `vello` in their crate dependencies.
a9f2971
to
0119c07
Compare
…feature (#10) linebender/vello#359 made `wgpu` an optional but default dependency/feature, but any crate using `vello_svg` will be forced to opt in to `wgpu` due to not disabling the default here. Since `vello_svg` does not need any rendering backend at all, this feature should be disabled by default. As the `vello` crate is reexported from the root, a `vello-wgpu` passthrough feature is provided so that users can turn it back on without explicitly depending on `vello` in their crate dependencies. Same change as linebender/velato#17.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
#10) linebender/vello#359 made `wgpu` an optional but default dependency/feature, but any crate using `vello_svg` will be forced to opt in to `wgpu` due to not disabling the default here. Since `vello_svg` does not need any rendering backend at all, this feature should be disabled by default. As the `vello` crate is reexported from the root, a `vello-wgpu` passthrough feature is provided so that users can turn it back on without explicitly depending on `vello` in their crate dependencies. Same change as linebender/velato#17.
wgpu
feature with an optional vello-wgpu
featurewgpu
feature with an optional wgpu
feature
linebender/vello#359 made
wgpu
an optional but default dependency/feature, but any crate usingvelato
will be forced to opt in towgpu
due to not disabling the default here.Since
velato
does not need any rendering backend at all, this feature should be disabled by default. As thevello
crate is reexported from the root, avello-wgpu
passthrough feature is provided so that users can turn it back on without explicitly depending onvello
in their crate dependencies.Note that
with_winit
runs briefly (withwgpu
), but if I don't manage to immediately fullscreen it, it panics:This is on a Wayland compositor with AMD GPU. I'm not a WGPU expert and don't dare to immediately say where it is being used wrong.