Missing libsystemd when building from custom image recipe.

[Charlie9830]

Hi @jwinarske.

Firstly thank you for the work you have put into this repo. I am relatively new to Yocto, I have been building a solution based off your work here for the past few weeks. Up until now the majority of my configuration exists within local.conf, adding my own recipes and building using bitbake core-image-base.

It's come to a point where I want to make my own image recipe based off core-image-base. And move most of the config out of local.conf before things get to unmanageable.

Broadly speaking, I created my a new layer with an image recipe that pulls in core-image-base via require. Moved a lot of the specific configuration (originally from this repo) into that recipe, adjusted references to CORE-IMAGE-EXTRA etc, removed references to the specific configuration details from local.conf and rebuilt using the custom image recipe. However the flutter-pi and sony embedder build tasks fail with cmake unable to locate libsystemd.

It however works if the specific config is instead inside local.conf and I build using bitbake core-image-base.

Below I have included the custom image recipe, the original working local.conf and finally the build output from bitbake when trying to build from the custom image recipe.

Does anything stand out to you that would be causing the build failure?

Custom Image Recipe

SUMMARY = "Castboard image for Development purposes"

LICENSE="MIT"

require recipes-core/images/core-image-base.bb

IMAGE_FEATURES += "splash debug-tweaks ssh-server-dropbear"

# Jwinarske stuff - https://github.com/jwinarske/meta-flutter
BBMASK = "meta-networking/recipes-kernel/wireguard"
DISTRO_FEATURES_remove = " sysvinit"
DISTRO_FEATURES_append = " alsa bluetooth usbhost opengl vulkan systemd wifi"
INIT_MANAGER = "systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""
DISTRO_FEATURES_append=" pam selinux"
DISTRO_FEATURES_BACKFILL_CONSIDERED = ""
COMBINED_FEATURES += "alsa "
MACHINE_FEATURES_remove = "apm"
PREFERRED_PROVIDER_jpeg = "libjpeg-turbo"
PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"
IMAGE_INSTALL += " packagegroup-core-selinux   avahi-daemon   vulkan-loader vulkan-tools   adwaita-icon-theme-cursors   xdg-user-dirs "
PREFERRED_VERSION_pipewire = "0.3.22"

# RPI Specific Configuration
DISABLE_OVERSCAN = "1"
DISABLE_RPI_BOOT_LOGO = "1"
DISABLE_SPLASH = "1"
ENABLE_SPI_BUS = "1"
ENABLE_I2C = "1"
ENABLE_UART = "0"
SERIAL_CONSOLES = ""

GPU_MEM = "128"
KERNEL_MODULE_AUTOLOAD_raspberrypi4-64 += "i2c-dev i2c-bcm2708"
DISPMANX_OFFLINE = "1"
LINUX_KERNEL_TYPE = "preempt-rt"
CMDLINE_DEBUG = "quiet"
PREFERRED_VERSION_linux-raspberrypi = "5.4.%"

# Flutter
FLUTTER_CHANNEL = "dev"

#
# User Facing Software
#

# Flutter Embedders
IMAGE_INSTALL_append = " flutter-pi"

# Flutter Applications
IMAGE_INSTALL_append = " castboard-player"

Original Working 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. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for 
# demonstration purposes:
#
#MACHINE ?= "beaglebone-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86-64 if no other machine is selected:
MACHINE ?= "raspberrypi4-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 ?= "/media/usb/yocto-cache/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 ?= "/media/usb/yocto-cache/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"

#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing 
# these defaults.
#
DISTRO ?= "poky"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream 
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"

#
# 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 rpm:
PACKAGE_CLASSES ?= "package_rpm"

#
# 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.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#
# 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"

#
# Yocto Project SState Mirror
#
# The Yocto Project has prebuilt artefacts available for its releases, you can enable
# use of these by uncommenting the following line. This will mean the build uses
# the network to check for artefacts at the start of builds, which does slow it down
# equally, it will also speed up the builds by not having to build things if they are
# present in the cache. It assumes you can download something faster than you can build it
# which will depend on your network.
#
#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"

#
# Qemu configuration
#
# By default native qemu will build with a builtin VNC server where graphical output can be
# seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
# 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.
#ASSUME_PROVIDED += "libsdl2-native"

# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
# a handy set of menus for controlling the emulator.
#PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"

#
# 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"

# 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"

# SPECIFIC CONFIGURATION

# HOST MACHINE BUILD
BB_NUMBER_THREADS ?= "6"
PARALLEL_MAKE = "-j 6"

# OUTPUT IMAGE TYPE
IMAGE_FSTYPES = "ext3.xz rpi-sdimg"

# jwinarske Stuff
INHERIT += "rm_work"

BBMASK = "meta-networking/recipes-kernel/wireguard"

DISTRO_FEATURES_remove = " sysvinit"
DISTRO_FEATURES_append = " alsa bluetooth usbhost opengl vulkan systemd wifi"

INIT_MANAGER = "systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""

DISTRO_FEATURES_append=" pam selinux"
DISTRO_FEATURES_BACKFILL_CONSIDERED = ""

COMBINED_FEATURES += "alsa "
MACHINE_FEATURES_remove = "apm"

PREFERRED_PROVIDER_jpeg = "libjpeg-turbo"
PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"

# DRM Fixes
#IMAGE_INSTALL_append = " kernel-modules"

# RPI Specific Configuration
DISABLE_OVERSCAN = "1"
DISABLE_RPI_BOOT_LOGO = "1"
DISABLE_SPLASH = "1"
ENABLE_SPI_BUS = "1"
ENABLE_I2C = "1"
ENABLE_UART = "0"
SERIAL_CONSOLES = ""

GPU_MEM = "128"
KERNEL_MODULE_AUTOLOAD_raspberrypi4-64 += "i2c-dev i2c-bcm2708"
DISPMANX_OFFLINE = "1"
LINUX_KERNEL_TYPE = "preempt-rt"
CMDLINE_DEBUG = "quiet"
PREFERRED_VERSION_linux-raspberrypi = "5.4.%"

CORE_IMAGE_EXTRA_INSTALL += "   packagegroup-core-selinux   avahi-daemon   vulkan-loader vulkan-tools   adwaita-icon-theme-cursors   xdg-user-dirs "

PREFERRED_VERSION_pipewire = "0.3.22"
FLUTTER_CHANNEL = "dev"

# SSH Server
IMAGE_FEATURES_append = " ssh-server-dropbear"

#
# User Facing Software
#

# Flutter Embedders
IMAGE_INSTALL_append = " flutter-pi"
IMAGE_INSTALL_append = " flutter-drm-gbm-backend"

# Flutter Applications
IMAGE_INSTALL_append = " castboard-player"

Output from bitbake cb-image-dev (Custom Image recipe)

Loading cache...done.
Loaded 3754 entries from dependency cache.
Parsing recipes...WARNING: /media/usb/rpi_64_yocto/sources/meta-flutter/recipes-graphics/flutter-apps/flutter-sdk-native_git.bb: Unable to get checksum for flutter-sdk-native-native SRC_URI entry ca-certificates.crt: file could not be found
done.
Parsing of 2530 .bb files complete (2526 cached, 4 parsed). 3760 targets, 149 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for runtime refpolicy (refpolicy-mcs, refpolicy-minimum, refpolicy-mls, refpolicy-standard, refpolicy-targeted)
Consider defining a PREFERRED_RPROVIDER entry to match refpolicy

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "raspberrypi4-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.9"
TUNE_FEATURES        = "aarch64 cortexa72 crc crypto"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "HEAD:12725e44c1f6217f9d1b337e2d7c0094bd96017b"
meta-raspberrypi     = "HEAD:59c2d6f7a8b1239bd7b587b9180c2a55f9c695a2"
meta-filesystems     
meta-oe              
meta-multimedia      
meta-networking      
meta-python          
meta-perl            
meta-webserver       = "HEAD:7bd47ef6c98323c95a9e527129dca98c9a65ee08"
meta-security        = "HEAD:6466c6fb02f36f459b06d434484df26e083f3489"
meta-selinux         = "HEAD:c9de7989464c7cd774e25d23496ed63ffc4ecdf6"
meta-qt5             = "HEAD:b4d24d70aca75791902df5cd59a4f4a54aa4a125"
meta-jumpnow         = "HEAD:b3995636741be0d219a50035c98ded8b48590888"
meta-clang           = "HEAD:e63d6f9abba5348e2183089d6ef5ea384d7ae8d8"
meta-rust            = "HEAD:494d879a1d337cda5b3a19406cabe46fcd3aee76"
meta-flutter         = "HEAD:a794c540ea61d1b48613a4c28105d109e061a339"
meta-autorun         = "master:763bd80348f7a8f2cc69bb14d6189dff49681177"
meta-cb-networking   = "<unknown>:<unknown>"
meta-castboardimage  = "master:64fc1d80d1a252a5b4c34a584c9ff94d5b3b32f8"

Initialising tasks...done.
Sstate summary: Wanted 28 Found 21 Missed 7 Current 2020 (75% match, 99% complete)
NOTE: Executing Tasks
NOTE: Running task 3665 of 5328 (/media/usb/rpi_64_yocto/sources/meta-flutter/recipes-graphics/flutter-pi/flutter-pi_git.bb:do_configure)
NOTE: recipe flutter-pi-git-r0: task do_configure: Started
Log data follows:
| DEBUG: Executing shell function do_configure
| -- CMAKE_BUILD_TYPE not set, defaulting to Release.
| -- The C compiler identification is GNU 9.3.0
| -- Check for working C compiler: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc
| -- Check for working C compiler: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc -- works
| -- Detecting C compiler ABI info
| -- Detecting C compiler ABI info - done
| -- Detecting C compile features
| -- Detecting C compile features - done
| -- Generator .............. Ninja
| -- Build Type ............. Release
| -- Flutter Channel not set, defaulting to stable
| -- Flutter Channel ........ stable
| -- Engine SHA1 ............ 241c87ad800beeab545ab867354d4683d5bfb6ce
| -- PKG_CONFIG_PATH ........
| -- Found PkgConfig: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/pkg-config (found version "0.29.2")
| -- Checking for module 'libdrm'
| --   Found libdrm, version 2.4.101
| -- Checking for module 'gbm'
| --   Found gbm, version 20.0.2
| -- Checking for module 'egl'
| --   Found egl, version 20.0.2
| -- Checking for module 'glesv2'
| --   Found glesv2, version 20.0.2
| -- Checking for module 'libsystemd'
| --   No package 'libsystemd' found
| CMake Error at /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:467 (message):
|   A required package was not found
| Call Stack (most recent call first):
|   /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:647 (_pkg_check_modules_internal)
|   CMakeLists.txt:95 (pkg_check_modules)
| 
| 
| -- Configuring incomplete, errors occurred!
| See also "/media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/temp/run.do_configure.80930' failed with exit code 1:
| -- CMAKE_BUILD_TYPE not set, defaulting to Release.
| -- The C compiler identification is GNU 9.3.0
| -- Check for working C compiler: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc
| -- Check for working C compiler: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc -- works
| -- Detecting C compiler ABI info
| -- Detecting C compiler ABI info - done
| -- Detecting C compile features
| -- Detecting C compile features - done
| -- Generator .............. Ninja
| -- Build Type ............. Release
| -- Flutter Channel not set, defaulting to stable
| -- Flutter Channel ........ stable
| -- Engine SHA1 ............ 241c87ad800beeab545ab867354d4683d5bfb6ce
| -- PKG_CONFIG_PATH ........
| -- Found PkgConfig: /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/bin/pkg-config (found version "0.29.2")
| -- Checking for module 'libdrm'
| --   Found libdrm, version 2.4.101
| -- Checking for module 'gbm'
| --   Found gbm, version 20.0.2
| -- Checking for module 'egl'
| --   Found egl, version 20.0.2
| -- Checking for module 'glesv2'
| --   Found glesv2, version 20.0.2
| -- Checking for module 'libsystemd'
| --   No package 'libsystemd' found
| CMake Error at /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:467 (message):
|   A required package was not found
| Call Stack (most recent call first):
|   /media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/recipe-sysroot-native/usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:647 (_pkg_check_modules_internal)
|   CMakeLists.txt:95 (pkg_check_modules)
| 
| 
| -- Configuring incomplete, errors occurred!
| See also "/media/usb/rpi_64_yocto/raspberrypi4-64/tmp/work/aarch64-poky-linux/flutter-pi/git-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: exit code 1 from a shell command.
| 
NOTE: recipe flutter-pi-git-r0: task do_configure: Failed
NOTE: Tasks Summary: Attempted 5309 tasks of which 5308 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /media/usb/rpi_64_yocto/sources/meta-flutter/recipes-graphics/flutter-pi/flutter-pi_git.bb:do_configure
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

[jwinarske]

Hi @Charlie9830

Are you following the steps in the readme?

Raspberry PI 3/4 (aarch64)

export MACHINE=raspberrypi4-64

or

export MACHINE=raspberrypi3-64

mkdir rpi_yocto && cd rpi_yocto
repo init -u https://github.com/jwinarske/manifests.git -m rpi64.xml -b dunfell
repo sync -j20
source ./setup-environment $MACHINE
bitbake-layers add-layer ../sources/meta-clang ../sources/meta-flutter
echo -e 'FLUTTER_CHANNEL = "dev"' >> conf/local.conf
echo -e 'IMAGE_INSTALL_append = " flutter-pi"' >> conf/local.conf
echo -e 'IMAGE_INSTALL_append = " flutter-gallery"' >> conf/local.conf
bitbake core-image-minimal

[Charlie9830]

Hi Joel, I was lacking in some of my own knowledge of Yocto and Bitbake, specifically Variable contexts and where they can be declared, Package recipes vs Image Recipes vs Distro recipes etc.

I have fixed the issue now. Thankyou, closing this now.