Yocto Project Summit 2025.12

Yocto and Bitbake Tooling
2025-12-02 , Whinlatter

Many tools and scripts are made available to developers after sourcing the build environment. These tools can automate many everyday Yocto tasks and greatly improve the Yocto experience.

This talk will briefly demonstrate how to automate common Yocto workflows for managing projects, managing dependency relationships, patching source code, etc. using tools such as bitbake, bitbake-*, oe-*, etc.


Many of the basic everyday Yocto tasks can be tedious. That is why the many amazing developers contributing to the Yocto project have created tools that come with Yocto to automate such tedious tasks.

Often beginners can end up wasting time on small issues for simple changes for example:

Creating a recipe but the recipe is not detected.
Creating a bbappend that fails to append.
Creating a layer but the layer configuration is not correctly defined.
Setting a variable but it does not take affect.

Often there are manual approaches to tasks such as creating layer and recipes by hand which can lead to such issues as above. The standard Yocto tooling can automate manual tasks that can be error prone for beginners thus avoiding such errors.

This talk will briefly cover the following Yocto and Bitbake tools:

  • bitbake-layers
  • bitbake-getvar
  • bitbake
  • recipetool
  • runqemu
  • oe-depends-dot
  • oe-pkgdata-util
  • oe-run-native
  • buildhistory-collect-srcrevs

To fullfill tasks such as:
- creating a Yocto project from scratch
- creating layers
- adding third party layers
- validating layer and recipe definitions
- determining inter-layer, inter-recipe, inter-task dependencies
- creating reproducible builds
- inspecting build environments
- patching recipe source code
- debugging the kernel
- emulating the kernel
- inspecting packages
- running native tooling without installing locally
- version locking all floating SRCREVs

See also:

I am Anakin Childerhose, an embedded software developer with a love for open source everything. I work at Savoir-faire Linux as an open source software consultant. I am obsessed with the terminal and will not rest until every workflow can be done from inside Vim.

This speaker also appears in: