On Wed, 28 Jan 2026 at 21:03, Weber (US), Matthew L via lists.openembedded.org <[email protected]> wrote: > Does my understanding as follows sound correct? Yocto doesn't provide a > binary distro, so we first build with Yocto from source, e.g., a small > generic x86 kernel and then setup a feed of kernel module pkgs and pkg world. > Can I assume a user's only option to build a system, would be to boot a > system to use the feed "online" to make a rootfs have everything they need? > Or are there more options for composing offline so the end users grabs a > kernel and a script that pulls a rootfs together offline from > emulation/hw/yocto env?(debootstrap like)
Making a complete product image offline with bitbake, from recipes in layers, is actually the primary way Yocto works. Embedded world isn't really using package feeds and package managers, rather you run bitbake to make an image that contains a complete product, and you flash it to a device. There are all sorts of software update mechanisms, but by an large they all operate with complete images as well, often in a A/B partition scheme. The reason 'classical' desktop distributions have to start with a minimal bootstrap, and do the rest on the system itself is that they do not have offline cross-compile support based on sysroot directories. Yocto does. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2218): https://lists.openembedded.org/g/openembedded-architecture/message/2218 Mute This Topic: https://lists.openembedded.org/mt/117514584/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
