Core Wayland window system code and protocol
Find a file
Demi Marie Obenour 64b9c5e1fd Merge branch 'message-size-test' into 'main'
tests: Test that an overlong message is rejected

See merge request wayland/wayland!486
2026-02-13 02:19:08 -05:00
.gitlab/issue_templates
cursor
doc doc: restore missing image files in docbook 2026-02-12 15:45:57 +01:00
egl
protocol protocol: reindent wayland.xml 2026-02-02 14:54:52 +02:00
src Merge branch 'message-size-test' into 'main' 2026-02-13 02:19:08 -05:00
tests Merge branch 'message-size-test' into 'main' 2026-02-13 02:19:08 -05:00
.editorconfig editorconfig: follow wayland-protocols XML style 2026-01-22 11:08:28 +02:00
.git-blame-ignore-revs fix .git-blame-ignore-revs revision 2026-02-02 14:00:28 +01:00
.gitignore
.gitlab-ci.yml doc: add meson.build for book 2026-02-12 15:17:33 +01:00
.mailmap
.triage-policies.yml
CONTRIBUTING.md
COPYING
git-blame-ignore-revs add .git-blame-ignore-revs file 2026-02-02 14:54:52 +02:00
meson.build doc: Refactor the build system for complete build dir docs 2025-11-27 17:39:11 +02:00
meson_options.txt doc: make DocBook validation optional 2026-02-04 15:12:04 +00:00
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.