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
Hi Christian,
On 10/24/22 13:05, Christian Thießen via lists.openembedded.org wrote:
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
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
If I run the same build again, no tasks will be executed, and
accordingly nothing in tmp/deploy will change:
alex@Zen2:/srv/work/alex/poky/build-64$ bitbake core-image-minimal
...
NOTE: Tasks Summary: Attempted 2862 tasks of which 2862 didn't need to
be rerun and all succeeded.
alex@Zen2:/srv/wor
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
Generally, you should not be deleting things from tmp/deploy (or tmp/
for that matter) - either delete all of tmp/ and rely on sstate or
don't touch it at all, and just re-run the build.
It helps if you provide steps to reproduce this behavior.
Alex
On Mon, 24 Oct 2022 at 10:36, Christian Thieße
(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
