Building

To start a full build, e.g. for the Kirkstone release, run the following command:

kas build kas/leda-qemux86-64.yaml

kas will then check out all necessary dependencies as specified in the project configuration file. After that, it will start the build for the machine, distro and target device.

Running

Running with user-level networking, in case the host does not have TAP/TUN set up properly. If you have TAP/TUN set up, remove the slirp keyword. Also enable the OVMF bios for multiboot. If you have kvm enabled on your host, add the kvm keyword:

kas shell kas/leda-qemux86-64.yaml -c 'runqemu nographic ovmf kvm'

Boot directly into a specific partition:

kas shell kas/leda-qemux86-64.yaml -c 'runqemu slirp nographic ovmf sdv-image-all'
kas shell kas/leda-qemux86-64.yaml -c 'runqemu slirp nographic ovmf sdv-image-full'
kas shell kas/leda-qemux86-64.yaml -c 'runqemu slirp nographic ovmf sdv-image-minimal'
kas shell kas/leda-qemux86-64.yaml -c 'runqemu slirp nographic ovmf sdv-image-rescue'

Debugging BitBake

The following commands show the layer setup and information about which recipes are being appended:

kas shell kas/leda-qemux86-64.yaml -c 'bitbake-layers show-layers'
kas shell kas/leda-qemux86-64.yaml -c 'bitbake-layers show-overlayed'
kas shell kas/leda-qemux86-64.yaml -c 'bitbake-layers show-recipes'
kas shell kas/leda-qemux86-64.yaml -c 'bitbake-layers show-appends'
kas shell kas/leda-qemux86-64.yaml -c 'bitbake -c cleanall '

Mirrors and Build Caching

In general, run a BitBake Hash Equivalence Server centrally.

Using the cache to improve build performance

To use our project cache, include the mirrors.yaml configuration file when building:

kas build kas/leda-qemux86-64.yaml:kas/mirrors.yaml

Updating the build cache

On a central build authoritative server, run the following commands to pre-download sources tar balls and fill up the downloads cache.

Pre-Requisites:

• Create the following repository secrets. The secret access key can be obtained via Azure Portal:

  AZURE_STORAGE_ACCESS_KEY="" AZURE_STORAGE_ACCOUNT="sdvyocto"

• Performing the same steps for the sstate-cache to improve build performance.

  Ask BitBake to perform only the fetch tasks for each recipe, downloading the sources

  and archiving them as a tar archive in the build/downloads/ folder.

  kas shell kas/leda-qemux86-64.yaml:kas/generate-mirror.yaml -c 'bitbake --runall=fetch sdv-image-all'

  Respectively, for other machines:

  kas shell kas/leda-raspberrypi4-64.yaml:kas/generate-mirror.yaml -c 'bitbake --runall=fetch sdv-image-all'

  Upload the downloads folder to the remote mirror.

  In this example, an Azure Blob Storage is used

  mkdir /tmp/downloads export TEMPD=$(mktemp -d) blobfuse2 --disable-version-check mount /tmp/downloads --use-https=true --tmp-path=${TEMPD} --container-name=downloads cp -v build/downloads/*.tar.gz /tmp/downloads/

Generation of SBOM

To generate Software Bill of Material documents (in SPDX format), run the kas tooling with the spdx configuration:

kas build kas/spdx.yaml

This will automatically include the configuration for Kirkstone release and using mirrors to speed up build time.