Core Wayland window system code and protocol
Find a file
Kristian Høgsberg a2c79b14a1 tests: Wrap calloc by just returning NULL if we're called too early
Since glibc dlsym() calls calloc, we get a call to our calloc wrapper as
we try to look up the real calloc implementation.  dlsym() will fall back
to a static buffer in case calloc returns NULL, so that's what we'll do.

This is all highly glibc dependent, of course, but the entire malloc
weak symbol wrapper mechanism is, so there's no loss of generality here.
2012-07-23 20:14:33 -04:00
cursor cursor: fix fd leak and a segfault 2012-07-10 14:11:00 -04:00
doc doc: fix some typos in documentation 2012-07-09 18:03:56 -04:00
m4 Clean up .gitignore files 2010-11-11 20:11:27 -05:00
protocol protocol: Add transform argument to wl_output.geometry event 2012-07-22 15:50:37 -04:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src connection: reserve id on incoming new object 2012-07-22 14:09:51 -04:00
tests tests: Wrap calloc by just returning NULL if we're called too early 2012-07-23 20:14:33 -04:00
.gitignore .gitignore: Add ctags and cscope files 2012-07-23 16:40:38 -04:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac cursor: use os_create_anonymous_file() 2012-07-10 14:08:59 -04:00
COPYING Add COPYING 2012-04-25 10:12:21 -04:00
Makefile.am Introduce libwayland-cursor, a cursor helper library 2012-05-22 15:20:13 -04:00
README README: Update 2012-07-20 12:20:20 -04:00
TODO protocol: Add transform argument to wl_output.geometry event 2012-07-22 15:50: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 applications, 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 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.