On Fri, Nov 11, 2022 at 8:36 AM Richard Purdie <[email protected]> wrote: > > On Fri, 2022-11-11 at 14:25 +0100, Rasmus Villemoes via > lists.openembedded.org wrote: > > On 10/11/2022 21.32, Paul Eggleton via lists.openembedded.org wrote: > > > Hi Richard > > > > > > On Thursday, 10 November 2022 11:14:24 NZDT Richard Purdie wrote: > > > > > > Adding in yet further if/else paths with magic variables to control > > > > them isn't filling me with confidence. > > > > > > I understand that. I was hoping to figure out a way to avoid adding > > > significant > > > extra complexity. > > > > > > > FWIW, we've long since given up on using kernel-fitimage.bbclass, it is > > way to inflexible (e.g. there's no way to build two FIT images with the > > same kernel but different initramfs). > > > > It is much simpler to just have a separate small kernel-fit.bb recipe > > which pulls vmlinux or Image or whatnot, plus the .dtbs, from > > DEPLOY_DIR_IMAGE along with the initramfs images, provide our own .its > > file(s), and build the FIT image(s) there. That automatically avoids > > rebuilding the kernel when only something in initramfs has changed. > > > > Building the kernel and packaging the binary into some container format > > really doesn't need to be done in the same recipe. > > I'm open to the idea of changing it to do that as that is how I'd > prefer it worked. I don't use it or know much about the needs people > have so I end up guided by others though...
I'm of a like mind. We've been wanting to re-work and clean up a LOT of the kernel classes for quite some time, but with all of the different workflows (and lack of tests) it is hard to get it right, and not break someone's case. I've been working through Paul's suggested patch, and I agree that it does try to minimize the copying of the kernel build artifacts, but the complication to the class and build is inevitable. I've also done multiple packaging and wrapping of boot artifacts outside of a single recipe, to avoid both complexity and extra building. I'm wondering if your classes are something you can cleanup and share ? That would help the discussion as we could talk about some tangible new approaches. Bruce > > Cheers, > > Richard > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173140): https://lists.openembedded.org/g/openembedded-core/message/173140 Mute This Topic: https://lists.openembedded.org/mt/94747626/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
