Core Wayland window system code and protocol
Find a file
Simon Ser aa88321517 protocol: add note about wl_output.done in events
Mention that geometry, mode and scale wl_output events are followed
by a done event.

Signed-off-by: Simon Ser <contact@emersion.fr>
2021-10-28 14:03:04 +00:00
.gitlab/issue_templates
cursor build: Include the Wayland minor version in libraries' ABI versions 2021-10-28 12:46:06 +00:00
doc
egl build: Include the Wayland minor version in libraries' ABI versions 2021-10-28 12:46:06 +00:00
protocol protocol: add note about wl_output.done in events 2021-10-28 14:03:04 +00:00
src build: Include the Wayland minor version in libraries' ABI versions 2021-10-28 12:46:06 +00:00
tests server: stop wl_display event loop from any context 2021-10-09 13:09:04 +00:00
.editorconfig
.gitignore
.gitlab-ci.yml gitlab-ci: add a FreeBSD test job 2021-09-10 11:35:54 +00:00
CONTRIBUTING.md
COPYING
meson.build build: Include the Wayland minor version in libraries' ABI versions 2021-10-28 12:46:06 +00:00
meson_options.txt
publish-doc
README
releasing.txt
wayland-scanner.m4
wayland-scanner.mk

What is 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.

The weston compositor is a reference implementation of a wayland
compositor and the weston repository also includes a few example
clients.

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 more complete build instructions
for wayland, weston, xwayland and various toolkits.