-
Notifications
You must be signed in to change notification settings - Fork 3k
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
enable building without X11 for Wayland-only systems #3340
Comments
|
you can take a look on upstream issue right there rust-windowing/winit#774 . |
|
Actually I feel like there's no need to disable something in winit. It seems like we can achieve it just inside alacritty. |
|
If someone is interested in testing the build it'll be nice to check #3436. Instructions are on the PR. |
|
Not directly related to this fix... But FWIW, I left a comment on rust-lang/cargo#5015 (comment), and opened a thread Rust Internals - Features and Workspaces, Request for Meta Issue. |
This commit adds two cargo features `x11` and `wayland` to pick Linux/BSD backends, with both enabled by default. Fixes #3340.
install man page introduce X and wayland useflags, this should allow to have alacritty without most X related dependencies on wayland-only systems See: alacritty/alacritty#3340 See: alacritty/alacritty#3436 Package-Manager: Portage-2.3.93, Repoman-2.3.20 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
This commit adds two cargo features `x11` and `wayland` to pick Linux/BSD backends, with both enabled by default. Fixes alacritty#3340.
Hi,
I wanted to build Alacritty on a Gentoo box that doesn't have any X11 libs installed. This failes because some X libs are linked to.
I tried to brute-force my way around this by removing all X-related dependencies and code. Unfortunately I'm stuck at
alacritty/alacritty/src/main.rs
Line 169 in 988a846
because there's no waylandish version of this implemented.
Any help in getting this awesome terminal running on Wayland-only is very much appreciated 😉
Thanks!
The text was updated successfully, but these errors were encountered: