Skip to main content
This section covers how to sync and build the meta-qcom release snapshot using the meta-qcom-releases repository. This workflow is deprecated and users are recommended to build using the default approach recommended in the Yocto Build Guide.

​
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 Yocto and the supporting meta layers. For the latest <meta-qcom-release-tag>, see Configuration Parameters. 
    git clone https://github.com/qualcomm-linux/meta-qcom-releases -b <meta-qcom-release-tag>

    kas checkout meta-qcom-releases/lock.yml
  • Copy the kas lock file from meta-qcom-releases to meta-qcom. Run this step, or the checked-out meta layers may update to a newer commit. 
    cp meta-qcom-releases/lock.yml meta-qcom/ci/lock.yml
  • Build the software image using kas. You define build targets based on machine and distro combinations. 
    kas build meta-qcom/ci/iq-9075-evk.yml:meta-qcom/ci/qcom-distro.yml:meta-qcom/ci/performance.yml:meta-qcom/ci/lock.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