Build a custom image from Reference Image with Yocto Project

Hi everyone,

I was following this tutorial’s step : OpenEmbedded (core) - Toradex System/Computer on Modules that I have achieved by building tdx-reference-minimal-image with success.
Then my next step is to build another image with qt5 layers and to remove x11 and wayland. So that I can run my qt app with eglfs platform by editing local.conf and bblayers as below :
local.conf :

 #
    # This file is your local configuration file and is where all local user settings
    # are placed. The comments in this file give some guide to the options a new user
    # to the system might want to change but pretty much any configuration option can
    # be set in this file. More adventurous users can look at local.conf.extended
    # which contains other examples of configuration which can be placed in this file
    # but new users likely won't need any of them initially.
    #
    # Lines starting with the '#' character are commented out and in some cases the
    # default values are provided as comments to show people example syntax. Enabling
    # the option is a question of removing the # character and making any change to the
    # variable as required.
    
    #
    # Machine Selection
    #
    # You need to select a specific machine to target the build with. These are the
    # machines which target the Toradex Apalis, Colibri and Verdin computer on
    # module families:
    #
    #MACHINE ?= "apalis-imx6"
    #MACHINE ?= "apalis-imx8"
    #MACHINE ?= "apalis-imx8x"
    #MACHINE ?= "apalis-tk1"
    #
    MACHINE ?= "colibri-imx6"
    ACCEPT_FSL_EULA = "1"
    #MACHINE ?= "colibri-imx6ull"
    #MACHINE ?= "colibri-imx7"
    #MACHINE ?= "colibri-imx7-emmc"
    #MACHINE ?= "colibri-imx8x"
    #
    #MACHINE ?= "verdin-imx8mm"
    #
    # There are also a selection of emulated machines available which can boot and run
    # in the QEMU emulator:
    #
    #MACHINE ?= "qemuarm"
    #MACHINE ?= "qemumips"
    #MACHINE ?= "qemuppc"
    #MACHINE ?= "qemux86"
    #MACHINE ?= "qemux86-64"
    
    #
    # Where to place downloads
    #
    # During a first build the system will download many different source code tarballs
    # from various upstream projects. This can take a while, particularly if your network
    # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
    # can preserve this directory to speed up this part of subsequent builds. This directory
    # is safe to share between multiple builds on the same machine too.
    #
    # The default is a downloads directory under TOPDIR which is the build directory.
    #
    DL_DIR ?= "${TOPDIR}/../downloads"
    
    #
    # Where to place shared-state files
    #
    # BitBake has the capability to accelerate builds based on previously built output.
    # This is done using "shared state" files which can be thought of as cache objects
    # and this option determines where those files are placed.
    #
    # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
    # from these files if no changes were made to the configuration. If changes were made
    # to the configuration, only shared state files where the state was still valid would
    # be used (done using checksums).
    #
    # The default is a sstate-cache directory under TOPDIR.
    #
    SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"
    
    #
    # Where to place the build output
    #
    # This option specifies where the bulk of the building work should be done and
    # where BitBake should place its temporary files and output. Keep in mind that
    # this includes the extraction and compilation of many applications and the toolchain
    # which can use Gigabytes of hard disk space.
    #
    # The default is a tmp directory under TOPDIR.
    #
    #TMPDIR = "${TOPDIR}/tmp"
    
    #
    # Where to place images and sw packages
    #
    # This places the build output in parallel to build and layers thus
    # if you have several build directories you need to adjust deploy
    # to something unique, e.g. "${TOPDIR}/../deploy_fb" "${TOPDIR}/../deploy_x11"
    DEPLOY_DIR = "${TOPDIR}/deploy"
    
    #
    # Package Management configuration
    #
    # This variable lists which packaging formats to enable. Multiple package backends
    # can be enabled at once and the first item listed in the variable will be used
    # to generate the root filesystems.
    # Options are:
    #  - 'package_deb' for debian style deb files
    #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
    #  - 'package_rpm' for rpm style packages
    # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
    # We default to ipk:
    PACKAGE_CLASSES ?= "package_ipk"
    
    #
    # SDK target architecture
    #
    # This variable specifies the architecture to build SDK items for and means
    # you can build the SDK packages for architectures other than the machine you are
    # running the build on (i.e. building i686 packages on an x86_64 host).
    # Supported values are i686 and x86_64
    #SDKMACHINE ?= "i686"
    
    #
    # Extra image configuration defaults
    #
    # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
    # images. Some of these options are added to certain image types automatically. The
    # variable can contain the following options:
    #  "dbg-pkgs"       - add -dbg packages for all installed packages
    #                     (adds symbol information for debugging/profiling)
    #  "src-pkgs"       - add -src packages for all installed packages
    #                     (adds source code for debugging)
    #  "dev-pkgs"       - add -dev packages for all installed packages
    #                     (useful if you want to develop against libs in the image)
    #  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
    #                     (useful if you want to run the package test suites)
    #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
    #  "tools-debug"    - add debugging tools (gdb, strace)
    #  "eclipse-debug"  - add Eclipse remote debugging support
    #  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
    #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
    #  "debug-tweaks"   - make an image suitable for development
    #                     e.g. ssh root access has a blank password
    # There are other application targets that can be used here too, see
    # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
    # We default to enabling the debugging tweaks.
    # package-management deploys the package meta data of deployed packeges
    EXTRA_IMAGE_FEATURES ?= "debug-tweaks package-management"
    
    #
    # Additional image features
    #
    # The following is a list of additional classes to use when building images which
    # enable extra features. Some available options which can be included in this variable
    # are:
    #   - 'buildstats' collect build statistics
    #   - 'image-mklibs' to reduce shared library files size for an image
    #   - 'image-prelink' in order to prelink the filesystem image
    # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
    # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
    USER_CLASSES ?= "buildstats image-mklibs image-prelink"
    
    #
    # Runtime testing of images
    #
    # The build system can test booting virtual machine images under qemu (an emulator)
    # after any root filesystems are created and run tests against those images. It can also
    # run tests against any SDK that are built. To enable this uncomment these lines.
    # See classes/test{image,sdk}.bbclass for further details.
    #IMAGE_CLASSES += "testimage testsdk"
    #TESTIMAGE_AUTO_qemuall = "1"
    
    #
    # Interactive shell configuration
    #
    # Under certain circumstances the system may need input from you and to do this it
    # can launch an interactive shell. It needs to do this since the build is
    # multithreaded and needs to be able to handle the case where more than one parallel
    # process may require the user's attention. The default is iterate over the available
    # terminal types to find one that works.
    #
    # Examples of the occasions this may happen are when resolving patches which cannot
    # be applied, to use the devshell or the kernel menuconfig
    #
    # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
    # Note: currently, Konsole support only works for KDE 3.x due to the way
    # newer Konsole versions behave
    #OE_TERMINAL = "auto"
    # By default disable interactive patch resolution (tasks will just fail instead):
    PATCHRESOLVE = "noop"
    
    #
    # Disk Space Monitoring during the build
    #
    # Monitor the disk space during the build. If there is less that 1GB of space or less
    # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
    # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
    # of the build. The reason for this is that running completely out of space can corrupt
    # files and damages the build in ways which may not be easily recoverable.
    # It's necesary to monitor /tmp, if there is no space left the build will fail
    # with very exotic errors.
    BB_DISKMON_DIRS ??= "\
        STOPTASKS,${TMPDIR},1G,100K \
        STOPTASKS,${DL_DIR},1G,100K \
        STOPTASKS,${SSTATE_DIR},1G,100K \
        STOPTASKS,/tmp,100M,100K \
        ABORT,${TMPDIR},100M,1K \
        ABORT,${DL_DIR},100M,1K \
        ABORT,${SSTATE_DIR},100M,1K \
        ABORT,/tmp,10M,1K"
    
    #
    # Shared-state files from other locations
    #
    # As mentioned above, shared state files are prebuilt cache data objects which can
    # used to accelerate build time. This variable can be used to configure the system
    # to search other mirror locations for these objects before it builds the data itself.
    #
    # This can be a filesystem directory, or a remote url such as http or ftp. These
    # would contain the sstate-cache results from previous builds (possibly from other
    # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
    # cache locations to check for the shared objects.
    # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
    # at the end as shown in the examples below. This will be substituted with the
    # correct path within the directory structure.
    #SSTATE_MIRRORS ?= "\
    #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
    #file://.* file:///some/local/dir/sstate/PATH"
    
    
    #
    # Qemu configuration
    #
    # By default qemu will build with a builtin VNC server where graphical output can be
    # seen. The two lines below enable the SDL backend too. By default libsdl2-native will
    # be built, if you want to use your host's libSDL instead of the minimal libsdl built
    # by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
    PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
    PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
    #ASSUME_PROVIDED += "libsdl2-native"
    
    #
    # Hash Equivalence
    #
    # Enable support for automatically running a local hash equivalence server and
    # instruct bitbake to use a hash equivalence aware signature generator. Hash
    # equivalence improves reuse of sstate by detecting when a given sstate
    # artifact can be reused as equivalent, even if the current task hash doesn't
    # match the one that generated the artifact.
    #
    # A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
    #
    #BB_HASHSERVE = "auto"
    #BB_SIGNATURE_HANDLER = "OEEquivHash"
    
    
    # Toradex fitImage support (For EMMC modules)
    #
    # To enable fitimage, uncomment the following two lines
    #
    # KERNEL_CLASSES_append = " toradex-fitimage"
    # KERNEL_IMAGETYPE_forcevariable = "${@'zImage' if d.getVar('TORADEX_FLASH_TYPE') == 'rawnand' else 'fitImage'}"
    
    
    # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
    # track the version of this file when it was generated. This can safely be ignored if
    # this doesn't mean anything to you.
    CONF_VERSION = "1"
    
    # Delete the the source/object/binary files once a package is built to preserve disk space
    INHERIT += "rm_work"
    
    # Add Toradex source mirror
    INHERIT += "toradex-mirrors"
    
    # Use this distro
    DISTRO = "tdx-xwayland"

    # meta-freescale otherwise defaults to wayland
    DISTRO_FEATURES_remove = "x11 wayland"
    
    
    EXTRA_USERS_PARAMS = "usermod -P root root;"
    IMAGE_INSTALL_append = " qtbase qtdeclarative qtimageformats qtmultimedia qtquick1 qtquickcontrols2 qtquickcontrols qtwebkit qtwebsockets sqlite3 libsqlite3 libsqlite3-staticdev libsqlite3-dev python3"
    PACKAGECONFIG_append_pn-qtbase = " sql-sqlite fontconfig"
    
    # Don't generate the mirror tarball for SCM repos, the snapshot is enough
    # BB_GENERATE_MIRROR_TARBALLS = "0"
    
    # This file does not need to exist, if it does it can be used to influence machine specific
    # configurations without copying the machine file.
    include conf/machine/include/${MACHINE}.inc

bblayer.conf

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  ${TOPDIR}/../layers/meta-toradex-nxp \
  ${TOPDIR}/../layers/meta-freescale \
  ${TOPDIR}/../layers/meta-freescale-3rdparty \
  \
  ${TOPDIR}/../layers/meta-toradex-tegra \
  \
  ${TOPDIR}/../layers/meta-toradex-bsp-common \
  \
  ${TOPDIR}/../layers/meta-openembedded/meta-oe \
  ${TOPDIR}/../layers/meta-openembedded/meta-filesystems \
  ${TOPDIR}/../layers/meta-openembedded/meta-gnome \
  ${TOPDIR}/../layers/meta-openembedded/meta-xfce \
  ${TOPDIR}/../layers/meta-openembedded/meta-initramfs \
  ${TOPDIR}/../layers/meta-openembedded/meta-networking \
  ${TOPDIR}/../layers/meta-openembedded/meta-multimedia \
  ${TOPDIR}/../layers/meta-openembedded/meta-python \
  ${TOPDIR}/../layers/meta-freescale-distro \
  ${TOPDIR}/../layers/meta-toradex-demos \
  ${TOPDIR}/../layers/meta-qt5 \
  \
  \
  ${TOPDIR}/../layers/meta-toradex-distro \
  ${TOPDIR}/../layers/meta-yocto/meta-poky \
  ${TOPDIR}/../layers/openembedded-core/meta \

Unfortunately bitbake process has stopped with the following error :
Nothing PROVIDES ‘vulkan-loader’ (but /home/vtran/oe-core/build/…/layers/meta-toradex-nxp/backports/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.imx.bb DEPENDS on or otherwise requires it) vulkan-loader was skipped: one of ‘wayland x11’ needs to be in DISTRO_FEATURES

Have you any idea to get me out of this situation knowing that I want the lightest image possible with everything I need to run a qt app with EGLFS platform.

Thank you for your answers.
BR,
Vanessa

Hi

Have you checked below post

https://www.toradex.com/community/questions/40800/imx6-with-mainline-kernel-and-etnaviv-for-eglfs.html

Please check and let us know if that help resolving the issue.

Best Regards

Ritesh kumar