Wayland dependencies are pulled in for eframe, even when `wayland` feature is disabled.
- Dominant language
- Rust
- Stars
- 30.6k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 72
Description
**Describe the bug**
When depending on eframe with default features disabled, and only `x11` and `glow` enabled, eframe is pulling in wayland dependencies.
**To Reproduce**
Create a new project, and depend on `eframe` with default features disabled.
```toml
[package]
name = "myeframetest"
version = "0.1.0"
edition = "2021"
[dependencies]
eframe = { git = "https://github.com/emilk/egui.git", default-features = false, features = ["glow", "x11"] }
```
**Expected behavior**
No wayland dependencies in `Cargo.lock`
**What happens**
`Cargo.lock` has several wayland dependencies.
Contributor guide
Research direction
Create the minimal project described in Cargo.toml with eframe default features disabled and only glow and x11 enabled. Inspect the generated Cargo.lock and eframe's feature configuration to identify why Wayland dependencies remain; done means the lockfile contains no Wayland dependencies for that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100