If the four devices have four separate MACHINE definitions in the BSP layer, then you'll have to build four different kernels.
I would look into why your custom software is dependent on the kernels and if that's really necessary. Typically userspace recipes are written in a way that their sstate output can be reused between different target machines, if those machines have the same architecture. Alex On Wed, 10 Jul 2024 at 12:52, philip.dawson via lists.yoctoproject.org <philip.dawson=datapath.co...@lists.yoctoproject.org> wrote: > > Hi, > > Sorry if this isn't a sensible question - I'm not quite familiar enough with > Yocto to be sure if what I'm asking for is sensible/possible. > > I'm currently building yocto (Through Xilinx Petalinux) for 4 related devices > and am looking to see if we can generate a single kernel and single rootfs > image for each board. > At the moment each board builds as a separate Petalinux project and the > combined build of all 4 takes a long time and the resulting images take up a > lot of disk space. > > Currently I'm not sure it's possible as there is a dependency chain from > device tree -> kernel -> modules/drivers -> our custom software. This means > the images are always different and the sstate cache for the > kernel/drivers/custom software is only valid for the board it's built against. > > Is there a way we can build one kernel for all four images even though they > will all need different device trees? > > Am I even asking the right question here? > > Best Regards, > Phil Dawson > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63453): https://lists.yoctoproject.org/g/yocto/message/63453 Mute This Topic: https://lists.yoctoproject.org/mt/107140139/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
