From: Tom Hochstein <[email protected]> When weston is started as the first windowing system (i.e. not under X nor under another Wayland server), it should be done with the command weston-launch to set up proper privileged access to devices.
Signed-off-by: Tom Hochstein <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> --- Changes in v7: None Changes in v6: - New patch. Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/recipes-graphics/wayland/weston-init/weston-start | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/meta/recipes-graphics/wayland/weston-init/weston-start b/meta/recipes-graphics/wayland/weston-init/weston-start index 17b0c16..2d398b6 100755 --- a/meta/recipes-graphics/wayland/weston-init/weston-start +++ b/meta/recipes-graphics/wayland/weston-init/weston-start @@ -31,6 +31,11 @@ if [ -n "$WAYLAND_DISPLAY" ]; then echo "ERROR: A Wayland compositor is already running, nested Weston instance is not supported yet." exit 1 fi +if [ -n "$DISPLAY" ]; then + launcher="weston" +else + launcher="weston-launch --" +fi openvt_args="" while [ -n "$1" ]; do @@ -64,4 +69,4 @@ if test -z "$XDG_RUNTIME_DIR"; then chmod 0700 $XDG_RUNTIME_DIR fi -exec openvt $openvt_args -- weston $weston_args --log=/var/log/weston.log +exec openvt $openvt_args -- $launcher $weston_args --log=/var/log/weston.log -- 2.8.2 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
