BoF: Multibuild for Zephyr RTOS
summary
Zephyr RTOS gains a non-recursive CMake approach that lets one top-level build include multiple application images via add_subdirectory plus a new image namespace and prefixed targets to avoid global name collisions; implementation lives in PR 13 672, is deployed by Nordic Semiconductor downstream, integrates with Segar embedded studio, reduces configure/link redundancy and enables parallel linking, and is reported to work in production while leaving toolchain-mixing and long-term maintenance tradeoffs unresolved.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:15Disclaimer
- 0:53Nordics solution
- 1:17Problem
- 2:05Usability
- 5:20Use Cases
- 6:35Semak
- 8:00Time Check
- 8:12Add Sub Directory
- 11:51Pros Cons
- 14:13Cons
- 16:38Recursive vs non recursive
- 18:08Recursive problems
- 18:57Linux kernel
- 24:59IBIS
- 25:39Flash layout
- 26:14Shared headers
- 26:37RPC calls
- 27:24How it works
- 28:19Big graph
- 28:49Yocto
- 29:29pippick
- 30:49other use cases
related talks
36mBoF: Multibuild for Zephyr RTOS
29mBuilding Zephyr using Yocto
40mConfiguring and Building a Heterogenous System Using the Yocto Project
26mBuilding for Heterogeneous Systems
01h 03mZephyr RTOS: Software power tools for constrained devices
48mBuild Zephyr for MicroBlaze-V FPGA Using Yocto Project
36mOne Build to Rule Them All: Building FreeRTOS & Linux Using Yocto
27mZephyr and Trusted Execution Environments