Core Wayland window system code and protocol
Find a file
Marek Chalupa b24fa4c821 tests: fix event_loop_timer_updates
It may happen that there's some time between the first and the other timer expire.
If epoll_wait is called after the first timer expired and
the other not, it returns only one source to dispatch and therefore
the test fails. To fix that, sleep a while before
wl_event_loop_dispatch() to make sure both timers expired.

To be 100% sure, we could use poll() before calling
wl_event_loop_dispatch(), but that would need modification in libwayland
(need to get the source's fd somehow)

https://bugs.freedesktop.org/show_bug.cgi?id=80594

Signed-off-by: Marek Chalupa <mchqwerty@gmail.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
2014-08-19 14:34:50 +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 protocol: add repeat_info event to wl_keyboard 2014-07-25 15:02:32 +03:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src event-loop: make signalfd non-blocking 2014-08-18 13:03:00 +03:00
tests tests: fix event_loop_timer_updates 2014-08-19 14:34:50 +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 client: extend error handling 2014-07-07 17:13:21 +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.