The struct weston_launcher object will now either handle tty and vt switching
details in-process (when running weston directly as root) or talk to
the weston-launch process.

Instead of the racy stat+open, open first and then use fstat.  We want to
make sure we're stating the fd we'll be sending to weston and nothing else.

Instead of a callback from the tty module, we now have a compositor level
signal that fires when our session is activated or deactivated.

We're going to add a bit more launcher state, so start out by creating
a new struct weston_launcher we can track it in.

This lets us detect hang-up when weston-launch dies and clean up properly.

Passing O_CLOEXEC to fcntl is wrong, we need to pass FD_CLOEXEC.

This tests (via the table-driven testing method) that the correct
number of vertices and also the correct vertices themselves
are generated for an clip box and polygon of up to eight vertices.

Also add a libshared-test.la so that we don't have to build weston-test-runner
all the time

The new TEST_P macro takes a function name and a "data" argument to
point to an arbitrary array of known size of test data. This allows
multiple tests to be run with different datasets. The array is stored
as a void * but advanced by a known size on each iteration.

The data for each invocation of the test is provided as a "data" argument,
it is the responsibility of the test to cast it to something sensible.

Also fixed single-test running to only run the tests specified

We are not building everything here as a module, only the test modules.

add a new function pointer to the weston_shell_interface struct that
shells will set accordingly.

Including listing the tests available in that binary

Slightly more readable and makes it easier to switch to use $2 for something
in the future (if that's ever needed).

check_PROGRAMS and friends are only built during make check. Which is a
great way of introducing compiler errors in tests. Always build them, TESTS
defines what's being run during make check.

Make vaapi_recorder take onwership of the fd and close it at destroy
time.

Previously, vaapi_recorder_frame() would wait until the encoded
contents for a frame is written to the output file descriptor. This
delayed the repainting of the next frame, and affected frame rate
when capturing with high resolutions. Instead, wait only if there is
and attempted to encode two frames at the same time.

Increases framerate from 30 to 60 fps when capturing at 1920x1200 on
my SandryBridge system, although there are periodic slowdowns due to
disk writes.

it uses the Android fbdev HAL[1] (through libhybris[2])
and the libhybris implementation of wayland-egl.

Configure flags:
 cairo:
   --enable-glesv2=yes  --enable-egl=yes
 weston:
   --with-cairo-glesv2 --enable-fbdev-compositor
 hybris:
   --enable-wayland --enable-arch=x86
   --with-android-headers=<android-headers> --enable-alinker=jb

The android headers are extracted from an AOSP tree,
using hybris/utils/extract-headers.sh

[1]:
https://github.com/android/platform_hardware_libhardware/blob/master/include/hardware/fb.h

[2]: https://github.com/libhybris/libhybrisSigned-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>

This is the current working directory of the shell as an URI.  We
don't use that for anythign at the moment, but let's not complain
about it at least.

Sorry, I missed updating use of xkb_info in compositor-x11.c.
I've updated the patch.

backend check the type of the framebuffer and accept DirectColor and TrueColor
I use a "switch case" to implement other cases in the future.

Hi Kristian,

Here's a new patch for ref counting weston_xkb_info, as suggested.
So a seat created with a NULL keymap will now point to the global xkb_info.

This way we do the right thing, when we get a NULL wl_resource for self-dnd.

Add missing return statement.

The call to source->send(source, mime_type, p[1]); dups the fd, and we have
to close p[1] to not leak it.

Typically we can write it immediately without blocking, so save the overhead
of setting up an fd watch and writing the data in a callback.  For the
case where the immediate write doesn't write all data, we fallback and
set up the fd watch as usual.

This patch also consolidates setting up the async write a bit.