Go to file
Matthias Clasen 53b57a63ee docs: Improve the wl_seat protocol docs
Expand the main description and tell if requests don't have
an effect.
2013-04-01 17:43:31 -04:00
cursor pkgconfig: Use configure provided directories 2012-11-27 20:35:50 -05:00
doc docs: Consistency fixes 2013-04-01 17:40:14 -04:00
m4 Clean up .gitignore files 2010-11-11 20:11:27 -05:00
protocol docs: Improve the wl_seat protocol docs 2013-04-01 17:43:31 -04:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src wayland-server: Avoid deferencing a NULL pointer in error case 2013-04-01 17:16:29 -04:00
tests Change wl_closure_invoke to take an opcode instead of an actual function pointer 2013-03-18 23:04:32 -04:00
.gitignore gitignore: add test-suite files 2013-01-24 16:14:52 -05:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac configure.ac: Use wayland_version macro in bug url 2013-03-17 13:53:29 -04:00
COPYING Add COPYING 2012-04-25 10:12:21 -04:00
Makefile.am Fix distcheck by adding back protocol/Makefile.am 2012-11-19 17:11:58 -05:00
README README: Fix typos 2013-02-14 12:14:54 -05:00
TODO Update TODO 2012-10-21 20:53:37 -04:00
wayland-scanner.m4.in Split into a core repository that only holds the core Wayland libraries 2011-02-14 22:21:13 -05:00
wayland-scanner.mk Split into a core repository that only holds the core Wayland libraries 2011-02-14 22:21:13 -05:00

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 git://anongit.freedesktop.org/wayland/wayland
    $ cd wayland
    $ ./autogen.sh --prefix=PREFIX
    $ make
    $ make install

where PREFIX is where you want to install the libraries.  See
http://wayland.freedesktop.org for more complete build instructions
for wayland, weston, xwayland and various toolkits.