Core Wayland window system code and protocol
Find a file
Derek Foreman 23e4a70600 client: Add new proxy marshalling functions with flags
There's a race when destroying wayland objects in a multi-threaded client.
This occurs because we call:
wl_proxy_marshal(foo);
wl_proxy_destroy(foo);

And each of these functions takes, and releases, the display mutex.
Between the two calls, the display is not locked.

In order to allow atomically marshalling the proxy and destroying the
proxy without releasing the lock, add yet more wl_proxy_marshal_*
functions.  This time add flags and jam in all existing warts with the
hope that we can make it future proof this time.

Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
2021-08-07 11:53:23 +00:00
.gitlab/issue_templates Add a basic gitlab issue template 2020-08-18 07:57:26 +00:00
cursor cursor: remove unused wl_cursor_theme.name 2021-08-06 09:26:03 +00:00
doc build: drop autotools 2021-03-05 09:15:04 +00:00
egl build: drop autotools 2021-03-05 09:15:04 +00:00
protocol protocol: clarify wl_seat.name description 2021-07-06 11:57:39 +00:00
src client: Add new proxy marshalling functions with flags 2021-08-07 11:53:23 +00:00
tests os-wrappers-test: Make syscall intercepts work with sanitizers 2021-07-22 22:27:45 +00:00
.editorconfig
.gitignore build: drop autotools 2021-03-05 09:15:04 +00:00
.gitlab-ci.yml ci: Sanitise build and install paths 2021-08-04 18:20:27 +01:00
CONTRIBUTING.md CONTRIBUTING: fix typo "excercising" 2020-12-17 16:03:14 -05:00
COPYING
meson.build build: add option to disable tests 2021-04-16 03:45:06 -06:00
meson_options.txt build: add option to disable tests 2021-04-16 03:45:06 -06:00
publish-doc
README
releasing.txt build: drop autotools 2021-03-05 09:15:04 +00:00
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.