Yocto build debug
Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug
Claude Agent Skills for Yocto Project, OpenEmbedded, and BitBake workflows - AI coding assistant skills for recipes, layers, images, BSPs, SDKs, metadata, QA, sstate, and build troubleshooting.
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-build-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Advanced Yocto Project build and debug skill for AI coding agents. Use for BitBake parse failures, fetch failures, patch/configure/compile/install/package failures, QA errors, missing providers, layer dependency errors, sstate/hash/signature problems, long build times, disk pressure, host dependency issues, TMPDIR confusion, and commands such as bitbake, bitbake-layers, bitbake -e, bitbake -g, bitbake-diffsigs, devtool, oe-pkgdata-util, runqemu, and testimage.
SKILL.md
2.1 KB, as published. Nobody here has run it
Yocto Build Debug
Workflow
- Identify the build entrypoint: Makefile,
kas,repo,oe-init-build-env, container script, CI job, or vendor wrapper. - Confirm
MACHINE,DISTRO,BBLAYERS,TMPDIR,DL_DIR,SSTATE_DIR, and target image/recipe. - Reproduce the smallest failing command. Prefer parse, fetch, or one task over a full image rebuild.
- Inspect logs before editing metadata. Use yocto_log_triage.py with the build directory for a quick scan.
- Classify the failure: parse, layer, provider, fetch, patch, configure, compile, install, package, QA, image, test, or signature.
- Route metadata questions to
$bitbake-metadata; route board boot/deploy issues to$yocto-deploy-flashor$yocto-bsp-bringup.
Commands
bitbake-layers show-layers
bitbake-layers show-recipes RECIPE
bitbake-layers show-appends
bitbake -e RECIPE
bitbake -c listtasks RECIPE
bitbake -c TASK -f RECIPE
bitbake -g RECIPE
bitbake-diffsigs SIGDATA_A SIGDATA_B
oe-pkgdata-util list-pkgs
References
- failure-playbook.md: failure categories and fixes.
- performance-cache.md: sstate, downloads, disk, parallelism, and reproducibility debugging.
Guardrails
- Do not recommend deleting
tmp/orsstate-cache/until narrower evidence has been checked. - Do not silence QA with
INSANE_SKIPuntil the package/file/license root cause is known. - Do not assume deploy output is under
tmp/; many builds usetmp-glibc, multiconfig paths, or customTMPDIR. - Do not change provider/version policy globally without checking affected recipes and images.