eada8e1379
This is to sync a recent change from libXcursor: https://gitlab.freedesktop.org/xorg/lib/libxcursor/-/merge_requests/22 The motivation is to unify the cursor scaling behavior in various X11 and Wayland apps / toolkits. Currently, when the cursor theme doesn't have the requested size, not all clients scale the cursor by themselves, resulting in inconsistent cursor size across clients. This problem is especially evident in Wayland, as a HiDPI-enabled clients will request cursors in the size: "XCURSOR_SIZE * display scale" which greatly increases the chance that the cursor theme doesn't provide the requested size. Tested with Weston. With an updated libwayland-cursor.so, and env "XCURSOR_RESIZED=true", Weston renders the cursor scaled to any XCURSOR_SIZE. Signed-off-by: Jin Liu <m.liu.jin@gmail.com> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| cursor | ||
| doc | ||
| egl | ||
| protocol | ||
| src | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .triage-policies.yml | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| meson.build | ||
| meson_options.txt | ||
| README.md | ||
| release.sh | ||
| releasing.txt | ||
| wayland-scanner.m4 | ||
| wayland-scanner.mk | ||
Wayland
Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
The wayland protocol is essentially only about input handling and buffer management. The compositor receives input events and forwards them to the relevant client. The clients creates buffers and renders into them and notifies the compositor when it needs to redraw. The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor. However, the protocol does not handle rendering, which is one of the features that makes wayland so simple. All clients are expected to handle rendering themselves, typically through cairo or OpenGL.
Building the wayland libraries is fairly simple, aside from libffi, they don't have many dependencies:
$ git clone https://gitlab.freedesktop.org/wayland/wayland
$ cd wayland
$ meson build/ --prefix=PREFIX
$ ninja -C build/ install
where PREFIX is where you want to install the libraries.
See https://wayland.freedesktop.org for documentation.