Enable wgpu default features in eframe / egui_wgpu default features#7344
Enable wgpu default features in eframe / egui_wgpu default features#7344
Conversation
lucasmerlin
commented
Jul 11, 2025
lucasmerlin
commented
- Closes No available wgpu backends with eframe 0.32.0 on Windows 10 #7342
- related Add "metal" to correctly run on MacOS #7314
|
Preview available at https://egui-pr-preview.github.io/pr/7344-lucaswgpu-default-features |
|
I have also disabled the features that we enabled based on the cfg. I think we can just enable the default wgpu backends by default and if the eframe default features are disabled, we should enable no backends. Maybe someone wants to use the gl or vulkan wgpu backend on mac (not recommended but technically possible), then they wouldn't need the metal backend. |
Wumpf
left a comment
Wumpf
left a comment
There was a problem hiding this comment.
ah, so the idea is that if you want to have less wgpu features you'd just disable default features on eframe, enable egui-wgpu feature yourself and then opt in to wgpu features manually?
Sounds good, but I think it's not working with that yet - eframe's optional egui-wgpu dependency would need to set no-default-features. Best to try it out! I find building with --timings and checking the html output for activated features easiest for this
Default features are disabled via the workspace, that should do it right? Line 65 in fdcaff8 |
|
ah yeah, I think that should do it! I'll give it a quick spin just to be sure |
Wumpf
left a comment
Wumpf
left a comment
There was a problem hiding this comment.
sorry for dropping the ball on this!
Tested it on windows: the following configuration successfully gave me a Vulkan only build:
eframe = { path = "../egui/crates/eframe", default-features = false, features = [
"wgpu",
] }
wgpu = { version = "25", default-features = false, features = ["vulkan"] }
* This was broken in emilk#7344
2 participants
