bhrebec/xwayland-satellite
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
5 commits 1 branch 0 tags 731 KiB
Find a file
Supreeeme b8bd07ce93 Use -displayfd instead of signals for Xwayland readiness 
The -displayfd argument is much friendlier to testing and is generally
more stable. As a result, omitting the display argument to the program
will result in Xwayland searching for the next available display. This
also allows integration tests to run simultaneously and when there is
already an X server running on the system.

This commit also changes how the state of the program is communicated
with integration tests (via the RunData trait).
2024-05-16 00:50:10 -04:00
satellite Use -displayfd instead of signals for Xwayland readiness 2024-05-16 00:50:10 -04:00
testwl Add initial support for toplevel titles and app ids 2024-05-11 00:37:11 -04:00
wl_drm Initial commit 2024-04-29 00:30:06 -04:00
.gitignore Initial commit 2024-04-29 00:30:06 -04:00
Cargo.lock Use -displayfd instead of signals for Xwayland readiness 2024-05-16 00:50:10 -04:00
Cargo.toml Initial commit 2024-04-29 00:30:06 -04:00
LICENSE Initial commit 2024-04-29 00:30:06 -04:00
README.md Initial commit 2024-04-29 00:30:06 -04:00

README.md

xwayland-satellite

xwayland-satellite grants rootless Xwayland integration to any Wayland compositor implementing xdg_wm_base. This is particularly useful for compositors that (understandably) do not want to go through implementing support for rootless Xwayland themselves.

Usage

Run xwayland-satellite. You can specify an X display to use (i.e. :12). Be sure to set the same DISPLAY environment variable for any X11 clients. Because xwayland-satellite is a Wayland client (in addition to being a Wayland compositor), it will need to launch after your compositor launches, but obviously before any X11 applications.

Building

cargo build
cargo run