weston-init: Use weston-launch when starting weston as the first windowing system

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.

(From OE-Core rev: 76ed534267ed16677eeb86b85670338a1064a733)

Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Tom Hochstein 2016-05-18 13:40:47 -03:00 committed by Richard Purdie
parent 7b779c8c2a
commit 5fb0c1edce
1 changed files with 6 additions and 1 deletions

View File

@ -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