From: "Christian Thießen" <christian.thiessen@airbus.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: license manifest files effectively disappear when do_rootfs is not rerun
Date: Mon, 24 Oct 2022 04:05:14 -0700 [thread overview]
Message-ID: <1878.1666609514952259746@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj-p9vce2nRGHjKJ0-VqGEaF0Ed2X-YMgFkfos4zJDiEWA@mail.gmail.com>
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 manifests.
So another option for a workaround would be to exclude the image recipe from rm_work.
Christian
next prev parent reply other threads:[~2022-10-24 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 8:36 license manifest files effectively disappear when do_rootfs is not rerun Christian Thießen
2022-10-24 8:41 ` [OE-core] " Alexander Kanavin
2022-10-24 8:58 ` Christian Thießen
2022-10-24 9:40 ` [OE-core] " Alexander Kanavin
2022-10-24 11:05 ` Christian Thießen [this message]
2022-10-24 11:31 ` Quentin Schulz
2022-10-25 8:31 ` Christian Thießen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1878.1666609514952259746@lists.openembedded.org \
--to=christian.thiessen@airbus.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox