From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Saul Wold <sgw@linux.intel.com>,
<openembedded-core@lists.openembedded.org>,
<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH] kernel.bbclass: Add cleandirs for do_shared_workdir
Date: Wed, 22 Nov 2017 15:51:55 -0500 [thread overview]
Message-ID: <3a0e2cdc-ca8c-07ba-e27d-701e3e4f6154@windriver.com> (raw)
In-Reply-To: <20171122184724.21416-1-sgw@linux.intel.com>
On 2017-11-22 1:47 PM, Saul Wold wrote:
> Ensure we have a clean and empty STAGING_KERNEL_BUILDDIR (kernel-build-artifacts)
> before creating it, otherwise there might be older artifacts from a prior
> kernel build.
>
What's the actual error that this triggers ? It would be nice to
log it here in the commit message .. or at least a description
of the symptoms.
> [YOCTO #11880]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/classes/kernel.bbclass | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 756707a3c25..2a0a7707a14 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -400,6 +400,7 @@ emit_depmod_pkgdata() {
>
> PACKAGEFUNCS += "emit_depmod_pkgdata"
>
> +do_shared_workdir[cleandirs] += " ${STAGING_KERNEL_BUILDDIR}"
> do_shared_workdir () {
> cd ${B}
>
> @@ -655,8 +656,6 @@ kernel_do_deploy() {
> fi
> done
> }
> -do_deploy[cleandirs] = "${DEPLOYDIR}"
> -do_deploy[dirs] = "${DEPLOYDIR} ${B}"
This isn't clear to me. Why does cleaning the STAGING_KERNEL_BUILDDIR
as part of the do_shared_workdir mean that we no longer need the
clean before the deploy (as well as the deploy dir).
Bruce
> do_deploy[prefuncs] += "package_get_auto_pr"
>
> addtask deploy after do_populate_sysroot do_packagedata
>
next prev parent reply other threads:[~2017-11-22 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 18:47 [PATCH] kernel.bbclass: Add cleandirs for do_shared_workdir Saul Wold
2017-11-22 20:51 ` Bruce Ashfield [this message]
2017-11-26 22:44 ` Saul Wold
2017-11-27 4:52 ` Bruce Ashfield
2017-11-27 13:35 ` Bruce Ashfield
2017-11-27 18:38 ` Saul Wold
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=3a0e2cdc-ca8c-07ba-e27d-701e3e4f6154@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=sgw@linux.intel.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