<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yocto on Moonforge</title><link>https://www.moonforgelinux.org/tags/yocto/</link><description>Recent content in Yocto on Moonforge</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.moonforgelinux.org/tags/yocto/index.xml" rel="self" type="application/rss+xml"/><item><title>Modern Yocto Linux Best Practices</title><link>https://www.moonforgelinux.org/blog/2026/modern_yocto_linux_best_practices/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.moonforgelinux.org/blog/2026/modern_yocto_linux_best_practices/</guid><description>&lt;p>If you&amp;rsquo;ve been working with the &lt;a href="https://www.yoctoproject.org/">Yocto Project&lt;/a> for a while, you already know it&amp;rsquo;s the de facto standard for building custom embedded Linux distributions. What you might not know is how much the tooling around it has improved.&lt;/p>
&lt;p>Many teams adopted Yocto years ago and have kept roughly the same workflows ever since, copying setup scripts between projects, letting each developer figure out how to clone layers, and building releases manually on dedicated machines. These were the common patterns at the time, but by now they are just unnecessary friction.&lt;/p></description></item></channel></rss>