Re: [OE-core] license manifest files effectively disappear when do_rootfs is not rerun

2022-10-25 Thread Christian Thießen via lists . openembedded . org
I don't feel familiar enough with the inner workings of oe-core to decide what a good (robust, maintainable) solution would be, but I've created a bug report with some suggestions: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14946 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sen

Re: [OE-core] license manifest files effectively disappear when do_rootfs is not rerun

2022-10-24 Thread Christian Thießen via lists . openembedded . org
Thanks, you're right; a normal rebuild doesn't execute any tasks. I've now found that this is related to rm_work: If you enable it with INHERIT+=" rm_work" in local.conf, bitbake will rerun three tasks on each rebuild: populate_lic_deploy, rm_work and build. After that you get the missing manif

Re: [OE-core] license manifest files effectively disappear when do_rootfs is not rerun

2022-10-24 Thread Christian Thießen via lists . openembedded . org
I'm not deleting anything. Steps to reproduce would be: Build just about any image for any machine, as long as it uses the standard classes like license_image.bbclass. You'll get a build/tmp/deploy/licenses/${IMAGE}-${MACHINE} symlink pointing to build/tmp/deploy/licenses/${IMAGE}-${MACHINE}- con

[OE-core] license manifest files effectively disappear when do_rootfs is not rerun

2022-10-24 Thread Christian Thießen via lists . openembedded . org
(Cross-post: I first posted to https://lists.yoctoproject.org/g/yocto/message/58392, then realized that according to the poky readme this list is more appropriate. Sorry, beginner's mistake) Dear list, when building an image with a Yocto setup based on kirkstone, it seems I've come across an i