-
-
Notifications
You must be signed in to change notification settings - Fork 41
Description
I'm on the latest crates.io release of both iced-layershell(0.14.2) and iced (0.14.0).
I'm trying to use software rendering, with tiny-skia, as hardware acceleration would not benefit my app in any ways, and it just uses more memory. I disabled wgpu for both iced and iced-layershell like so:
[dependencies]
iced = {version = "0.14.0", default-features = false, features = ["debug", "fira-sans", "linux-theme-detection", "tiny-skia", "smol"]}
iced_layershell = { version = "0.14.2", default-features = false, features = ["debug", "fira-sans", "linux-theme-detection", "tiny-skia"]} Despite this, running cargo tree revealed that iced-renderer still has wgpu as it's dependency. I tried with a plane iced project, where i disabled the wgpu module, and it did not depend on wgpu. Since I don't have any other crate I suspect that iced-layershell is the reason wgpu gets included despite not being listed as an enabled feature.
I found a solution and set ICED_BACKEND env var to "tiny-skia" (ICED_BACKEND=tiny-skia cargo run), and from the memory usage it seems like it does use tiny-skia. (if ICED_BACKEND is set to software, it will panic tho, stating you need tiny-skia as a dependency, even tho you clearly have it).
I don't know if this is a serious enough bug, but I still wanted to share it for other who also want to use software rendering, but it'd be still nice to fix up the modules and make sure of wgpu isn't listed, it doesn't get compiled.