Local.conf for console build

Hello all,

This page:

…advises modifying local.conf as follows:

MACHINE ?= “colibri-imx6”
ACCEPT_FSL_EULA = “1”
DISTRO_FEATURES_remove = “x11 wayland”
IMAGE_INSTALL_remove = “eglinfo-x11”


…and then calling bitbake as follows:

$ bitbake console-trdx-image

Something I don’t understand though, is since we are building a console image, why is it necessary to remove the x11/wayland features, and the eglinfo-x11 package? Shouldn’t that already be the case for a console image?

Regards,
Richard.

Hi

If you would “just” build a console image you are right, but the article adds Qt5 functionality to the bare console image and then that stuff becomes needed.

Vivante provides libraries which allow the use of the GPU. Depending on the used backend these binaries are different and only the needed ones are installed.

The article you reference wants to make use of eglfs as the graphical backend for Qt and without removing “x11 wayland” you would get the libraries for x11 which would result in an unusable system.


IIRC due to some dependencies eglinfo-x11 would be installed and then would also fail because of dependencies.

Max

So if we weren’t adding Qt5 functionality (as per article), the removal of “x11 wayland” would not be required, for a console build? I.e. they wouldn’t be included in the first place?

Yes.

(The generic answer is that if you not use the GPU you don’t need to remove “x11 wayland”).

Max