![]() Jadahl has done some work as part of !2392 (closed) to split the X11/Wayland Barrier implementations.Ĭommand Line: Error out when Wayland/X11 specific backends options are used and the corresponding backend is disabled at build time Keybindings: Couldn't come up with an idea by looking at the code, maybe we could have a common base class and have different implementation per backend instead of a bunch of if(!is_wayland_compositor()) return all over the place It should be a matter of replacing gl pkg-config with glesv2. Use GLES instead of GL, it seems GL brings back x11 through GLX. At the end of the day, it also has an in-tree copy of xcursor. Using libwayland-cursor is not an option here as it doesn't allow us to get access to the internal Cursor type and rather give us a wl_buffer so we can't share the same code between X11/Wayland backends. We could have an in-tree copy of what we need from xcursor. ![]() This PR would also make GDK a X11 specific dependencyĬursor loading: Currently mutter uses xcursor which handles loading the cursor assets from the user theme. It would require a small patch to GNOME Shell (the infra from Mutter side is already handled on the PR below) so that the producer/consumer for key events is Mutter and no longer GTK. ![]() Remove GTK usage from libmutter as it brings X11 dependencies indirectly from GDK -> GDK X11 Move X11 windows frames to a separate client The goal of this issue is to track the various tasks in order to achieve that. Currently Mutter can't be built as a Wayland only compositor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |