Real-World Yocto: Getting the Most out of Your Build System
summary
Advice focuses on concrete tactics: split layers by distro, machine and UI to avoid painful upgrades; use Shared State Cache and sstate mirrors to reuse builds (one user cuts a full build to seven minutes); generate boot media with wic (OpenEmbedded Image Creator) and put images on SD fast with bmap-tools instead of dd; publish package feeds via bitbake-package-index so boards can rpm install new builds; use devtool, recipe-tool append-file, dumpcigs/diffcigs and bitbake -C to debug precisely.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:38Why use Yocto
- 3:49How to build useful software
- 7:37The Yocto project
- 11:33SState Cache
- 20:18File System
- 24:02Bitbake Options
- 26:28Bitbake Layers
- 29:48Pull Requests
- 31:11Bug Triage and Technical Meeting
- 34:09Do Installs
- 37:27Versioning Layers
- 39:55S State Cache
- 41:09S State Cache with multiple builds
- 41:46S State Cash
- 42:08S State Cash Uses
- 43:36Separation of Concerns
- 46:20Questions
- 47:21SState Mirror vs SState Directory
- 49:01Build Server
- 49:23Changes Test
- 51:04Last Chance
related talks
30mStrategies for Developing and Deploying your Embedded Applications and Images
24mDOs and DON'Ts when building a Yocto based distribution
43mProducing a Complete Linux System With a Single Command (and Configuration File) With Yocto
45mBuilding and Maintaining Binary Distributions with Yocto
42mSpeed-up bitbake with SSTATE, PRSERV and HashSERV
40mWhy the Yocto Project for My IoT Project
32mSoftware Supply Chain with the Yocto Project
49mThe 5 Key Success Factors to Deploy Yocto for “Production Grade” Embedded/IoT Devices