Hello Tom,
On Thu, Dec 17, 2015 at 8:04 PM, Tom Hochstein
<[email protected]> wrote:
> Weston is started in different ways depending on the image
> configuration and the runtime scenario. Refer to the weston man
> page for more information.
>
> Signed-off-by: Tom Hochstein <[email protected]>
I think we are quite close to something which works for all supported
use-cases. More below...
...
> @@ -13,6 +14,18 @@ do_install() {
>
> install -d ${D}${systemd_system_unitdir}
> install -m0644 ${WORKDIR}/weston.service ${D}${systemd_system_unitdir}
> +
> + install -d ${D}/${bindir}
> + install -m755 ${WORKDIR}/weston-start ${D}/${bindir}
> + if [ "${@bb.utils.contains('DISTRO_FEATURES', 'x11 wayland',
> 'xwayland', '', d)}" = "xwayland" ]; then
> + weston_launch_setup="mkdir -p /tmp/.X11-unix"
> + weston_launch_args="--modules=xwayland.so"
> + else
> + weston_launch_setup=""
> + weston_launch_args=""
> + fi
> + sed -i "s#WESTON_LAUNCH_SETUP#${weston_launch_setup}#"
> ${D}/${bindir}/weston-start
> + sed -i "s#WESTON_LAUNCH_ARGS#${weston_launch_args}#"
> ${D}/${bindir}/weston-start
We can do it at runtime and avoid using this hardcoded options?
One possibility is to check if XWayland is available. If it is, it can
enable those options.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
