Hello Tom, On Sat, Dec 19, 2015 at 4:08 PM, Tom Hochstein <tom.hochst...@freescale.com> wrote: > Can you be more explicit about what you mean by weston-launch wrapper? Do you > want to hide the current weston-launch binary and replace it by a new > weston-launch wrapper? What happens to my proposed weston-start, which is > itself a wrapper? Does its functionality move into weston-launch?
Yes; my proposal is to use weston-launch to hide the real binary and call it internally. This allows for everyone using weston-launch (even on terminal or serial console) to benefit from it otherwise people will be aware of the custom script. > Can you help me understand the rationale for the extra XWayland script? The > existing weston recipe installs xwayland.so when the XWayland package is > specified. In your proposal, the weston recipe would also install the extra > script when the XWayland package is specified. Since the same XWayland > package mechanism is used in both cases, the benefit of the extra script > isn't clear to me. Because it would allow for same distro to generate one XWayland based image[1] and another pure Wayland image[2]. 1. xserver-xorg-xwayland (a) -> weston-module-xwayland (b) So (a) includes the inner script which says to weston-launch wrapper to load the xwayland.so module. (b) is split out from normal weston package so it avoids unneeded runtime dependencies. 2. weston weston includes just the normal weston bits so allowing pure Weston images without manual changes. -- 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 Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
