2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2013-04-29 12:26:05 +02:00
|
|
|
#
|
|
|
|
|
# weston
|
|
|
|
|
#
|
2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2013-04-29 12:26:05 +02:00
|
|
|
|
2013-10-14 23:26:36 +02:00
|
|
|
WESTON_VERSION = 1.3.0
|
2013-04-29 12:26:05 +02:00
|
|
|
WESTON_SITE = http://wayland.freedesktop.org/releases/
|
2013-10-09 00:09:48 +02:00
|
|
|
WESTON_SOURCE = weston-$(WESTON_VERSION).tar.xz
|
2013-04-29 12:26:05 +02:00
|
|
|
WESTON_LICENSE = MIT
|
|
|
|
|
WESTON_LICENSE_FILES = COPYING
|
|
|
|
|
|
2013-10-09 00:09:49 +02:00
|
|
|
WESTON_DEPENDENCIES = host-pkgconf wayland libxkbcommon pixman libpng \
|
2013-05-24 15:44:49 +02:00
|
|
|
jpeg mtdev udev cairo
|
2013-10-10 23:05:21 +02:00
|
|
|
|
2013-10-14 23:26:36 +02:00
|
|
|
# We're touching Makefile.am
|
2013-10-10 23:05:21 +02:00
|
|
|
WESTON_AUTORECONF = YES
|
|
|
|
|
|
2013-04-29 12:26:05 +02:00
|
|
|
WESTON_CONF_OPT = \
|
|
|
|
|
--disable-egl \
|
2013-10-10 23:05:19 +02:00
|
|
|
--disable-simple-egl-clients \
|
2013-04-29 12:26:05 +02:00
|
|
|
--disable-xwayland \
|
|
|
|
|
--disable-x11-compositor \
|
|
|
|
|
--disable-drm-compositor \
|
|
|
|
|
--disable-wayland-compositor \
|
|
|
|
|
--disable-headless-compositor \
|
|
|
|
|
--disable-weston-launch \
|
package/weston: add RPi compositor
Procedure highly inspired by:
http://wayland.freedesktop.org/raspberrypi.html
The resulting weston works almost flawlessly, but requires a bit
of love:
- /boot/config.txt must include this line: dispmanx_offline=1
- at least 128MiB of RAM must be allocated to the GPU
- after 24-or-so terminal-clients are connected, the screen
turns black. Exiting a client restores the screen
It seems increasing/decreasing the amount of memory allocated to
the GPU makes the clients limit to wobble above/below 24 clients
at a time. YMMV, as they say...
Without dispmanx_offline=1, the limit is much below 24, at around 13.
But changing the amount of memory allocated to the GPU does not change
this limit in this case. YMMV, again.
Anyway, there are not many different clients available, besides the
terminal client, since all other clients are EGL-based, and there
is (yet) no EGL support (for weston!) on the RPi. So the tests were
made only with the terminal client.
The system is rather smooth, but spwaning too many clients in a
rapid-fire is sure to exhibit some lag. Resizing windows is a bit
jerky, but moving them along is fine.
Note: the config option has a depends on THREADS due to rpi-userland,
even though weston itself already inherits the same dependency from
wayland. But better be clean and safe.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-10 23:05:25 +02:00
|
|
|
--disable-colord \
|
2013-04-29 12:26:05 +02:00
|
|
|
--disable-libunwind
|
|
|
|
|
|
|
|
|
|
ifeq ($(BR2_PACKAGE_WESTON_FBDEV),y)
|
|
|
|
|
WESTON_CONF_OPT += --enable-fbdev-compositor
|
|
|
|
|
else
|
|
|
|
|
WESTON_CONF_OPT += --disable-fbdev-compositor
|
|
|
|
|
endif
|
|
|
|
|
|
package/weston: add RPi compositor
Procedure highly inspired by:
http://wayland.freedesktop.org/raspberrypi.html
The resulting weston works almost flawlessly, but requires a bit
of love:
- /boot/config.txt must include this line: dispmanx_offline=1
- at least 128MiB of RAM must be allocated to the GPU
- after 24-or-so terminal-clients are connected, the screen
turns black. Exiting a client restores the screen
It seems increasing/decreasing the amount of memory allocated to
the GPU makes the clients limit to wobble above/below 24 clients
at a time. YMMV, as they say...
Without dispmanx_offline=1, the limit is much below 24, at around 13.
But changing the amount of memory allocated to the GPU does not change
this limit in this case. YMMV, again.
Anyway, there are not many different clients available, besides the
terminal client, since all other clients are EGL-based, and there
is (yet) no EGL support (for weston!) on the RPi. So the tests were
made only with the terminal client.
The system is rather smooth, but spwaning too many clients in a
rapid-fire is sure to exhibit some lag. Resizing windows is a bit
jerky, but moving them along is fine.
Note: the config option has a depends on THREADS due to rpi-userland,
even though weston itself already inherits the same dependency from
wayland. But better be clean and safe.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-10 23:05:25 +02:00
|
|
|
ifeq ($(BR2_PACKAGE_WESTON_RPI),y)
|
|
|
|
|
WESTON_DEPENDENCIES += rpi-userland
|
|
|
|
|
WESTON_CONF_OPT += --enable-rpi-compositor \
|
|
|
|
|
--disable-resize-optimization \
|
|
|
|
|
--disable-setuid-install \
|
|
|
|
|
--disable-xwayland-test \
|
|
|
|
|
--disable-simple-egl-clients \
|
|
|
|
|
WESTON_NATIVE_BACKEND=rpi-backend.so
|
|
|
|
|
else
|
|
|
|
|
WESTON_CONF_OPT += --disable-rpi-compositor
|
|
|
|
|
endif # BR2_PACKAGE_WESTON_RPI
|
|
|
|
|
|
2013-04-29 12:26:05 +02:00
|
|
|
$(eval $(autotools-package))
|
