Embedded Linux Development Using Yocto ProjectBuild production-grade embedded Linux products with the Yocto Project 6.0… (Otavio Salvador, Daiane Angolini)（Z-Library）

【One-Line Pitch】 A hands-on field guide to building reproducible, production-grade embedded Linux with the Yocto Project 6.0 (Wrynose) LTS, taking you from a first QEMU boot to custom layers, SDKs, package feeds, and compliance-ready SBOMs. Best for embedded engineers and build/infrastructure developers comfortable on the Linux command line who need to ship and maintain real hardware products. 【Book Arc】 - **Opening (~0%–15%)**: Establishes the foundation — what the Yocto Project and OpenEmbedded layers are, how to bake a first image, and how to reproduce a build from a clean machine. It solves the "where do I even start" problem. - **Early (~15%–30%)**: Introduces the toolchain around the build: the VS Code BitBake extension, BitBake's role in the workflow, layer structure, and the three kinds of metadata you will meet everywhere afterward. - **Early–Middle (~30%–45%)**: Moves into the mechanics of metadata and packaging — dependency graphs, task scheduling, source fetching and mirrors, the temporary build directory, package formats, versioning, and runtime dependencies. - **Middle (~45%–65%)**: Deepens into authoring: custom layers, recipes, machines, and distributions, plus the Standard and Extensible SDKs for building applications and the Linux kernel. - **Late (~65%–85%)**: Turns to production operations — package feeds, Build History, devshell debugging, Toaster's web dashboard, QEMU emulation for faster iteration, and the new bitbake-setup / bitbake-config-build configuration workflows. - **Ending (~85%–100%)**: Closes on compliance and longevity — SPDX 3.0 SBOMs, CVE scanning, GPL/copyleft obligations, and a Best Practices chapter for keeping a product maintainable over a multi-year lifecycle. 【Key Takeaways】 - **Reproducibility is the whole point** (Opening): the early goal is a build any engineer can recreate from a clean machine, which becomes the baseline everything else depends on. - **Layers are the unit of organization** (Early): only BitBake and the `meta` layer are strictly required; `meta-yocto` layers are reference content, and production builds typically substitute their own distribution and BSP layers. - **Dependencies are expressed as task graphs** (Middle): `DEPENDS` and `RDEPENDS` declare build-time and runtime relationships, and BitBake schedules parallel work wherever prerequisites allow. - **Packaging sits at the center of every build** (Middle): images, SDKs, and feeds are all produced from consistent, versioned packages, with license metadata stamped onto each one. - **Versioning has three moving parts** (Middle): `PE:PV-PR` governs ordering and feed monotonicity, and the PR Service automates revision bumps for published feeds. - **SDKs are underused but powerful** (Late): the Standard SDK is described as commonly undervalued, while the Extensible SDK supports application and kernel development outside the full build. - **Compliance is a build output, not an afterthought** (Ending): SPDX 3.0 SBOMs and CVE scanning are framed as deliverables supporting EU CRA and U.S. EO 14028 reporting. - **Best practices protect multi-year maintenance** (Ending): manage layers deliberately, avoid too many layers or excessive kernel patches, avoid `AUTOREV` as `SRCREV`, and maintain the Shared State Cache. 【Reading Tips】 - Deep-read the metadata and packaging chapters (Middle); they are the conceptual hinge for everything later. Skim the tooling setup chapters if your host is already configured. - Treat the Best Practices chapter as a checklist to revisit before starting a real product, not as a one-time read. - The new BitBake configuration chapter (bitbake-setup, fragments, registries) is worth close attention if your team needs to share and reproduce builds across machines. - Watch for the Shared State Cache caveat: `cleanall` does not clear a shared sstate mirror, so a rebuild may skip `do_fetch` entirely — this surprises many readers. - Hardware chapters assume access to BeagleBone Black, Raspberry Pi 4/5, or VisionFive boards; use QEMU to follow along if you lack the hardware. 【Coverage Limits】 This guide is synthesized from stratified excerpts covering roughly the first half of the book plus the table of contents and preface; later chapters on SDKs, Toaster, package feeds, compliance, and best practices are summarized from headings and front matter rather than full text.