DOs and DON'Ts when building a Yocto based distribution
summary
Oniro shares concrete lessons: avoid creating an always-empty layer such as meta-oniro-staging because Yocto warns on empty layers; keep layer.conf dependencies accurate and prefer bbfiles_dynamic for conditional bbappends; never mix backported packages with local recipe changes — use backports as-is and add separate bbappend files so upgrades to Dunfell or Kirkstone don’t force manual surgery; run yocto-check-layer in CI, publish source even under permissive licenses, and collaborate upstream early rather than reworking large patches later.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:00What is your project
- 2:40Layers
- 4:37Layer depends
- 6:55Do write no surprises
- 9:14Understand and evaluate mixing layers
- 10:20Run Yocto Check Layer often
- 11:37Don'ts
- 12:25Don't forget
- 13:26Don't mix backports
- 14:36Release your source
- 15:38Upstream changes
- 17:03Conclusion
- 17:33Questions
related talks
53mReal-World Yocto: Getting the Most out of Your Build System
58mHow to write a really good board support package for Yocto Project
39mBoF: The Yocto Project and OpenEmbedded
20mUsing Yocto as a Method to Upstream, Maintain, and Track Patches
42mSetting up Yocto Layers and Builds with Official Tools – 2023 Edition
45mBuilding and Maintaining Binary Distributions with Yocto
42mBoF: The Yocto Project and OpenEmbedded
36mLessons Learned: Migrating a Production Platform to Yocto