On Mon, 2021-01-04 at 13:07 +0000, Diego Sueiro wrote: > For some arm based machines we end up generating loads of > intermediate binaries > which will be further processed and combined as standalone images, > for example. > I think doesn't make sense to have them in the deploy dir since it > will make it > polluted and I do much prefer to have a tidy deploy dir with only > artifacts for > flashing/update the target, rather than a list of useless artifacts > that can't be used > directly. > > And I do agree with you that using the SYSROOT_DIRS for this purpose > might lead > to confusion. Is it plausible to come up with a new variable and > do_populate related > tasks to address use cases like the one I described
Just thinking out loud, maybe we can use SYSROOT_DIRS if we use something which is named clearly such that its obvious it will never be on the target rootfs? "/boot" is confusing as some systems do have/use that but there is nothing stopping us creating something specific to this purpose. We'd have to clearly document it should never be used for anything also shared using do_deploy and was for intermediate files only? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#146354): https://lists.openembedded.org/g/openembedded-core/message/146354 Mute This Topic: https://lists.openembedded.org/mt/79420282/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
