66be76c169
Client message observers 1/6 Cleans up wl_closure_print(), and adds a client-private closure_log() intermediate function. This patch simplifies wl_closure_print() slightly by moving some client-only details to a new closure_log() intermediate function. This new function will also handle delivering messages to the new listener callback in a subsequent patch. closure_log() internally handles the check for logging being enabled, simplifying its callers, and returns early if logging is not enabled. This check becomes a bit more complex when there can be listeners. closure_log() also handles the work same transformation performed by id_from_object(), by making a copy of the args, and applying the transform to the copy before passing the arguments to wl_closure_print(). Doing it this way means the same arguments can also be passed to the eventual listeners. The boolean "discarded" argument for wl_closure_print() has been replaced by a "discarded_reason" string argument, allowing an arbitrary reason string to be passed in. For now only "discarded[]" is printed as an empty reason string is passed if the message was discarded, but that will also change. Signed-off-by: Lloyd Pique <lpique@google.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.