Skip to main content
The Yocto Build Guide covers how to build a stable and validated version of meta-qcom directly on the host. This guide explains how to run the same build inside a Docker container using kas-container, which eliminates the need to install Yocto build dependencies on your host machine and ensures a consistent, reproducible build environment.

​
Prerequisites

  • kas-container requires Docker to be installed and running on your host. Follow the official Docker documentation to get set up
  • kas-container is a wrapper script that ships alongside kas. When you install kas using pipx (as described in the Host Setup section of the Yocto Build Guide), kas-container is installed automatically into the same environment and is available on your PATH. Confirm if kas-container is available on the system 
    kas-container --version

​
Configuration Parameters

The following table describes the build tags for the current release. These values will be need to be substituted in the build commands.
Release TagIdentifier
meta-qcom-release-tagqli-2.0

​
Build Instructions

  • Download Qualcomm’s Yocto layer meta-qcom. For the latest <meta-qcom-release-tag>, see Configuration Parameters. 
    git clone https://github.com/qualcomm-linux/meta-qcom -b <meta-qcom-release-tag>
  • Build the software image using kas-container. You define build targets based on machine and distro combinations. 
    kas-container build meta-qcom/ci/iq-9075-evk.yml:meta-qcom/ci/qcom-distro.yml
  • The build creates a single tarball containing all the relevant files to perform a full clean flash, including partition metadata, boot firmware, ESP partition and the rootfs. After a successful build, check if the qcomflash tarball exists in the build artifacts. The following examples use qcom-multimedia-proprietary-image as the image name. 
    ls build/tmp/deploy/images/iq-9075-evk/qcom-multimedia-proprietary-image-iq-9075-evk.rootfs.qcomflash.tar.gz