-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Wayland build error without wayland feature #3038
Comments
Encountering the same issue cross-compiling windows -> aarch linux |
Good catch! BTW, you can figure out which crates causes a feature to be enabled with |
#3228 should solve it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm trying to run egui on an Olimex Allwinner A13 board which I'm running Linux 3.4.90 on. There is a few qt applications running, so I'm guessing that it has X11.
I have added eframe to my empty project using
cargo add eframe
. It shows that the featurewayland
isn't enabled:But when trying to build the project, it fails with a build error in
winit-0.28.6/src/platform_impl/linux/wayland/protocols.rs
:It seems like the
wayland
feature is getting enabled in thewinit
crate, even if not enabled ineframe
.(I also tested this using eframe from latest git master, same error)
To Reproduce
Steps to reproduce the behavior:
cargo init
cargo add eframe
main.rs
cargo build --release --target armv7-unknown-linux-musleabihf
Expected behavior
I expected no wayland-related build errors
Screenshots
n/a
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
n/a
The text was updated successfully, but these errors were encountered: