From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ccache: Ensure CCACHE_DIR is cleaned by do_clean task
Date: Mon, 09 Jul 2012 15:31:55 +0100 [thread overview]
Message-ID: <1341844315.8066.18.camel@ted> (raw)
In-Reply-To: <4FFAE9ED.3050505@windriver.com>
On Mon, 2012-07-09 at 09:25 -0500, Mark Hatle wrote:
> On 7/9/12 9:16 AM, Khem Raj wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 7/9/2012 4:55 AM, Richard Purdie wrote:
> >> This ensures a rebuild does really build from scratch when ccache
> >> is in use.
> >>
> >> [YOCTO #2696]
> >>
> >> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >> --- diff --git a/meta/classes/ccache.bbclass
> >> b/meta/classes/ccache.bbclass index 5aa2da2..cd06a4b 100644 ---
> >> a/meta/classes/ccache.bbclass +++ b/meta/classes/ccache.bbclass @@
> >> -4,3 +4,5 @@ CCACHE_DISABLE[unexport] = "1"
> >>
> >> do_configure[dirs] =+ "${CCACHE_DIR}" do_kernel_configme[dirs] =+
> >> "${CCACHE_DIR}" + +do_clean[cleandirs] += "${CCACHE_DIR}"
> >>
> >
> > so will this remove all contents of .ccache dir ?
> > or just the package you are cleanall'ing
>
> I was wondering the same thing, with the default configuration:
>
> bitbake.conf:# Assign CCACHE_DIR a default value to fix a bug of ccache 3.1.7,
> bitbake.conf:# since it would always create CCACHE_DIR/.ccache even if
> bitbake.conf:export CCACHE_DIR ??= "${@os.getenv('HOME')}"
That line is only in the class file and that class redefines CCACHE_DIR
to include PN.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-09 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 11:55 [PATCH] ccache: Ensure CCACHE_DIR is cleaned by do_clean task Richard Purdie
2012-07-09 14:16 ` Khem Raj
2012-07-09 14:25 ` Mark Hatle
2012-07-09 14:31 ` Richard Purdie [this message]
2012-07-09 14:27 ` Richard Purdie
2012-07-09 14:31 ` Mark Hatle
2012-07-09 14:48 ` Richard Purdie
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=1341844315.8066.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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