On 12/20/2013 02:36 AM, Saul Wold wrote:
On 12/19/2013 06:20 AM, Valentin Popa wrote:
For builds with fbdev (no drm/kms), set
WESTON_NATIVE_BACKEND to "fbdev-backend.so"; doing this,
weston-launch will be able to know what backend to use.
Signed-off-by: Valentin Popa <valentin.p...@intel.com>
---
meta/recipes-graphics/wayland/weston_1.3.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/wayland/weston_1.3.1.bb
b/meta/recipes-graphics/wayland/weston_1.3.1.bb
index d97f6af..4ab2776 100644
--- a/meta/recipes-graphics/wayland/weston_1.3.1.bb
+++ b/meta/recipes-graphics/wayland/weston_1.3.1.bb
@@ -45,7 +45,7 @@ PACKAGECONFIG[x11] =
"--enable-x11-compositor,--disable-x11-compositor,virtual/l
# Headless Weston
PACKAGECONFIG[headless] =
"--enable-headless-compositor,--disable-headless-compositor"
# Weston on framebuffer
-PACKAGECONFIG[fbdev] =
"--enable-fbdev-compositor,--disable-fbdev-compositor,udev mtdev"
+PACKAGECONFIG[fbdev] = "--enable-fbdev-compositor
WESTON_NATIVE_BACKEND="fbdev-backend.so",--disable-fbdev-compositor,udev
mtdev"
Is this a more general way to do this as suggested by Koen back in May?
+# Needed for weston-launch
+WESTONBACKEND ??= "fbdev-backend.so"
+
+export WESTON_NATIVE_BACKEND = "${WESTONBACKEND}"
See http://patches.openembedded.org/patch/50871/
Sau!
Not sure of the context of that patch, but with this patch we have fbdev
backend -only- if the user builds with fbdev distro feature.
I've tried to build with both kms and fbdev and failed at compile time
(bug or feature).
# weston-launch
PACKAGECONFIG[launch] =
"--enable-weston-launch,--disable-weston-launch,libpam"
# VA-API desktop recorder
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
