Go to file
Marek Chalupa 171e0bdace tests: test if thread can block on error
wl_display_read_events() can make a thread wait until some other thread
ends reading. Normally it wakes up all threads after the reading is
done. But there's a place when it does not get to waking up the threads
- when an error occurs. This test reveals bug that can block programs.

If a thread is waiting in wl_display_read_events() and another thread
calls wl_display_read_events and the reading fails,
then the sleeping thread is not woken up. This is because
display_handle_error is using old pthread_cond instead of new
display->reader_cond, that was added along with wl_display_read_events().

Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
2014-08-22 12:53:49 +03:00
cursor Add error handling for wl_cursors 2014-04-01 16:47:04 -07:00
doc doc: force publican to use fop 2014-07-06 12:39:16 +03:00
m4 Clean up .gitignore files 2010-11-11 20:11:27 -05:00
protocol wl_surface: clarify the base of time passed in the callback of frame 2014-08-21 10:01:17 +03:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src client: remove unused variable 2014-08-21 14:45:03 +03:00
tests tests: test if thread can block on error 2014-08-22 12:53:49 +03:00
.gitignore gitignore: Add another test-suite file 2014-07-25 16:09:44 +03:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac configure: fix publican version detection 2014-07-06 12:39:16 +03:00
COPYING Add COPYING 2012-04-25 10:12:21 -04:00
Makefile.am tests: add test-compositor 2014-08-22 12:34:33 +03: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.