Skip to main content
Legacy workflow. Qualcomm recommends the kas tool as the preferred way to build and consume meta-qcom. This repo-based workflow is retained only for existing setups already built around it. For new builds, use Build Qualcomm Linux using Yocto.
This section covers how to sync and build the meta-qcom release snapshot using the repo tool, for legacy users who are already familiar with it and need to continue supporting or maintaining existing setups. As part of this guide, you’ll
  • Install additional packages required for this workflow
  • Sync the meta layers required for the build using repo tool
  • Use the helper script to translate the kas configuration files into BitBake configuration files and setup the environment
  • Execute a Yocto build using native BitBake commands

​
Host Setup

  • These packages are required in addition to the default packages to perform a manifest based build. 
    sudo apt install repo python3-yaml

​
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 the Qualcomm Yocto and supporting layers using repo. For the latest <meta-qcom-release-tag>, see Configuration Parameters. 
    repo init -u https://github.com/qualcomm-linux/qcom-manifest -b qcom-linux-wrynose -m <meta-qcom-release-tag>.xml
repo sync
  • Set up the Yocto build environment using the helper script. This script expects kas configuration files to be passed as parameters and converts these kas configuration files into the auto.conf and bblayers.conf configuration required by BitBake 
    source setup-environment --machine meta-qcom/ci/iq-9075-evk.yml --distro meta-qcom/ci/qcom-distro.yml
  • Build the image by invoking BitBake 
    bitbake qcom-multimedia-proprietary-image
  • 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