Manifests: Project Sanity in the Ever-Changing Zephyr World
summary
Claim: project-level manifest files lock each component to a branch tag or commit so an application installs its own copy of Zephyr and libraries and reliably rebuilds months or years later. Tools used: West init/update, manifest inheritance, allow list / groups, West manifest --resolve and --freeze, and optional West commands for patches. Example outcome: repositories for Zephyr Golioth libraries and custom board defs get checked out into a depths folder, builds become reproducible, disk use rises but can be pruned, virtualenv recommended.
AI-written summary · about
chapters (13)
- 0:00Manifest files in Zephyr
- 2:29Manifest files essentials
- 5:57Zephyr main manifest
- 8:46Inheritance and allow lists
- 11:10West init and update
- 15:43Best practices for application development with manifests
- 18:54Build environment setup
- 21:02App setup with manifests
- 25:40External libraries
- 29:16Company code and revisions
- 31:24Advanced manifest features
- 34:15Custom West commands
- 36:01Why use manifest files
related talks
41mDemystifying West
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
36mHow to Get Your Zephyr Patches Merged
27mZephyr and You: A Developer Environment for Newcomers
32mLeveraging Cloud Technologies for Development and Operation of Zephyr
44mZephyr Build System: Sysbuild and New Hardware Model
33mContinues Integration Practices for Zephyr Upstream