f72e4797f4
If the environment variable WESTON_TEST_CLIENT_PATH is not set, do not quit Weston in the test plugin. This allows one to start Weston with the test plugin manually, and then run any tests also manually, while observing Weston's behaviour over time. This is useful for: - Running a test multiple times and checking if Weston leaks (e.g. with Valgrind) - Running tests manually on a backend that is not x11 or wayland, especially the backends that require weston-launch, and therefore cannot be used with the 'make check' machinery. This change should not affect 'make check' behaviour, because there WESTON_TEST_CLIENT_PATH is always set. Cc: U. Artie Eoff <ullysses.a.eoff@intel.com> Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Weston Weston is the reference implementation of a Wayland compositor, and a useful compositor in its own right. Weston has various backends that lets it run on Linux kernel modesetting and evdev input as well as under X11. Weston ships with a few example clients, from simple clients that demonstrate certain aspects of the protocol to more complete clients and a simplistic toolkit. There is also a quite capable terminal emulator (weston-terminal) and an toy/example desktop shell. Finally, weston also provides integration with the Xorg server and can pull X clients into the Wayland desktop and act as a X window manager. Refer to http://wayland.freedesktop.org/building.html for buiding weston and its dependencies.