Am Do, 19. Aug 2021, um 00:22, schrieb Khem Raj:
On Wed, Aug 18, 2021 at 3:06 PM Manuel Wagesreither <ManWag@...> wrote:
x11-* features is primarily to control what kind of x11 packages you
I'm building an image to run on various SBCs and would like to equip it with a graphical interface.
There are quite a few things very unclear to me. Can someone help me with that?
* Why is X11 enabled by setting an IMAGE_FEATURE (namely x11, x11-base or x11-sato), while Wayland is enabled by IMAGE_INSTALL only (weston-init and weston)?
want to include in image e.g.
pulled in when x11-sato is added to IMAGE_FEATURES
we have many X11 based images and sato is one of them so thats why its
you should really is looking at DISTRO_FEATURES e.g. wayland distro
feature is needed for core-image-weston to build.
* Theory: Is IMAGE_FEATURE +=x11 manipulating IMAGE_INSTALL under the hood so you don't have to do it manually? And as there is no IMAGE_FEATURE "wayland", you have do it manually. Correct?there are not many wayland based compositors or images we have in core
* Why is Wayland different in that it doesn't need an IMAGE_FEATURE to enable it?
as of now.
* Why does core-image-weston.bb need to enable IMAGE_FEATURE hwcodec, while core-image-x11.bb does not? (Dunfell branch.)openGL is needed for wayland/weston to work too but hwcodec feature is
infact to pull in machine specific drivers MACHINE_HWCODECS into image
if a given BSP defined it.
e.g. intel bsps define vaapi codecs and mediasdk for specific machines
defaults for this image features are empty
Hi Khem, thanks! will need to look into this and digest what you said.
Thanks, regards, Manuel