Building an Image
 | The Qualcomm Dragonwing Technical Guide documentation from RidgeRun is presently being developed. |
Build BSP Image
Overview
This section describes how to create and build a Yocto BSP image using Qualcomm Linux and kas.
Clone Qualcomm Yocto Meta Layers
Download the Qualcomm Yocto meta layers. Replace <meta-qcom-release> with the appropriate release tag.
git clone https://github.com/qualcomm-linux/meta-qcom-releases -b <meta-qcom-release>
Example:
git clone https://github.com/qualcomm-linux/meta-qcom-releases -b qli-2.0-rc2
 | lleon: Where can we find the releases? (please remove this box when addressed) |
Checkout kas Lock File
kas checkout meta-qcom-releases/lock.yml
Copy Lock File
Copy the kas lock file to ensure consistent layer versions.
cp meta-qcom-releases/lock.yml meta-qcom/ci/lock.yml
Build the Image
Define your build using machine and distribution configuration files.
kas build meta-qcom/ci/<machine.yml>:meta-qcom/ci/<distro.yml>:meta-qcom/ci/linux-qcom-6.18.yml:meta-qcom/ci/lock.yml
Example:
kas build meta-qcom/ci/iq-9075-evk.yml:meta-qcom/ci/qcom-distro-prop-image.yml:meta-qcom/ci/linux-qcom-6.18.yml:meta-qcom/ci/lock.yml
Remember to set up locales (specified on previous section), otherwise, might throw error:
Please make sure locale 'en_US.UTF-8' is available on your system 2026-04-07 13:32:53 - ERROR - Command "/home/ridgerun/bitbake/bin/bitbake -c build qcom-multimedia-image qcom-multimedia-proprietary-image qcom-container-orchestration-image" failed with error 1
| lleon: where can we find the distros? Change the example for the non-prop image (please remove this box when addressed) |
Verify Build Artifacts
After a successful build, verify that the root filesystem image exists.
cd <workspace-dir>/build/tmp/deploy/images/<MACHINE>/<IMAGE>-<MACHINE>.rootfs.qcomflash/
ls -al rootfs.img
| lleon: Add a way to find the machine and images (the list). Also, add an example (please remove this box when addressed) |
Compile single image
The previous command compiles the qcom-multimedia-image, qcom-multimedia-proprietary-image and qcom-multimedia-image. To compile a single available image, get into the the kas shell workspace by using:
kas build meta-qcom/ci/<machine.yml>:meta-qcom/ci/<distro.yml>:meta-qcom/ci/linux-qcom-6.18.yml:meta-qcom/ci/lock.yml
Example:
kas shell meta-qcom/ci/iq-9075-evk.yml:meta-qcom/ci/qcom-distro-prop-image.yml:meta-qcom/ci/linux-qcom-6.18.yml:meta-qcom/ci/lock.yml
And then:
bitbake <image>
Example:
bitbake qcom-minimal-image
| lleon: Same comment regarding the non-prop image (please remove this box when addressed) |
Notes
- Qualcomm Linux uses kas to sync meta layers, configure the environment, and run BitBake.
- You can use kas-container for isolated builds (requires Docker).
- Default storage (UFS or eMMC) depends on the machine configuration. See storage configuration docs to change it.
- For supported <machine> and <distro> combinations, refer to the Release Notes.
- For advanced workflows: