From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <pbarker@konsulko.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/5] archiver.bbclass: Make do_deploy_archives a recursive dependency
Date: Tue, 10 Mar 2020 23:18:33 +0000 [thread overview]
Message-ID: <a6f3718866f85a6208023b253bec26bf6b5d4172.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200309142139.15741-3-pbarker@konsulko.com>
On Mon, 2020-03-09 at 14:21 +0000, Paul Barker wrote:
> To ensure that archives are captured for all dependencies of a typical
> bitbake build we add do_deploy_archives to the list of recursive
> dependencies of do_build. Without this, archives may be missed for
> recipes such as gcc-source which do not create packages or populate a
> sysroot.
>
> do_deploy_archives is also added to the recursive dependencies of
> do_populate_sdk so that all sources required for an SDK can be captured.
>
> Signed-off-by: Paul Barker <pbarker@konsulko.com>
> ---
> meta/classes/archiver.bbclass | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/archiver.bbclass b/meta/classes/archiver.bbclass
> index fef7ad4f62..c11d36d708 100644
> --- a/meta/classes/archiver.bbclass
> +++ b/meta/classes/archiver.bbclass
> @@ -604,7 +604,9 @@ addtask do_ar_configured after do_unpack_and_patch
> addtask do_ar_mirror after do_fetch
> addtask do_dumpdata
> addtask do_ar_recipe
> -addtask do_deploy_archives before do_build
> +addtask do_deploy_archives
> +do_build[recrdeptask] += "do_deploy_archives"
> +do_populate_sdk[recrdeptask] += "do_deploy_archives"
We implemented the --runall option to bitbake to try and avoid having
recrdeptask versions of most tasks. Does that not work here? It should
also work for the SDK I think?
Cheers,
Richard
next prev parent reply other threads:[~2020-03-10 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 14:21 [PATCH 0/5] Archiver and externalsrc fixes Paul Barker
2020-03-09 14:21 ` [PATCH 1/5] archiver.bbclass: Handle gitsm URLs in the mirror archiver Paul Barker
2020-03-10 23:16 ` Richard Purdie
2020-03-11 11:31 ` Paul Barker
2020-03-11 11:38 ` Richard Purdie
2020-03-11 11:50 ` Paul Barker
2020-03-11 11:53 ` Richard Purdie
2020-03-09 14:21 ` [PATCH 2/5] archiver.bbclass: Make do_deploy_archives a recursive dependency Paul Barker
2020-03-10 23:18 ` Richard Purdie [this message]
2020-03-11 11:40 ` Paul Barker
2020-04-01 14:49 ` [OE-core] " Mark Hatle
[not found] ` <1601B99892621331.16702@lists.openembedded.org>
2020-04-01 17:20 ` Mark Hatle
2020-03-09 14:21 ` [PATCH 3/5] kernelsrc.bbclass: Fix externalsrc support Paul Barker
2020-03-09 14:21 ` [PATCH 4/5] perf: " Paul Barker
2020-03-09 14:21 ` [PATCH 5/5] kernel-yocto.bbclass: Support config fragments with externalsrc Paul Barker
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=a6f3718866f85a6208023b253bec26bf6b5d4172.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pbarker@konsulko.com \
/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