| commit | 84e872a0dc482bffdb63672969dd03a827d67c73 | [log] [tgz] |
|---|---|---|
| author | Lloyd Pique <[email protected]> | Fri May 03 00:01:22 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri May 03 00:01:22 2024 +0000 |
| tree | a24cc9a98b8d2a67e1f757d5652be03b710fa061 | |
| parent | 443fae79ac80d89257fd546d39d73daa5dfeee2f [diff] | |
| parent | b3a126671d7fdb9c45bb4f14ed34cd08fad8974d [diff] |
Update OWNERS am: 083ddb2e6d am: b3a126671d Original change: https://android-review.googlesource.com/c/platform/external/wayland/+/3073549 Change-Id: Iaea27be3903895dc6999b03ef30a8c470dcb22ba Signed-off-by: Automerger Merge Worker <[email protected]>
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.