Core Wayland window system code and protocol
Find a file
Pekka Paalanen 538ee6bed6 doc: do not rebuild man pages if they are up to date
The doxygen.man make target was not a real file that was generated,
therefore the man page rule was ran on every make invocation. Replace it
with a real file that is produced by the man page rule.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
2014-03-10 13:10:28 -07:00
cursor build: Move cursor Makefile.am into toplevel Makefile.am 2014-03-06 23:15:02 -08:00
doc doc: do not rebuild man pages if they are up to date 2014-03-10 13:10:28 -07:00
m4 Clean up .gitignore files 2010-11-11 20:11:27 -05:00
protocol build: Move protocol/ Makefile.am into toplevel Makefile.am 2014-02-18 14:55:09 -08:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src build: Move src/Makefile.am into toplevel Makefile.am 2014-03-07 11:50:59 -08:00
tests build: Move tests/Makefile.am into toplevel Makefile.am 2014-03-07 12:00:06 -08:00
.gitignore gitignore: add ./compile 2013-09-11 12:15:11 -07:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac build: Move tests/Makefile.am into toplevel Makefile.am 2014-03-07 12:00:06 -08:00
COPYING Add COPYING 2012-04-25 10:12:21 -04:00
Makefile.am build: depend on generated protocol headers 2014-03-10 13:10:10 -07: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 scanner: check for wayland-scanner.pc before using variables 2013-08-07 16:25:10 -07: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.