From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ccache: Ensure CCACHE_DIR is cleaned by do_clean task
Date: Mon, 9 Jul 2012 09:31:43 -0500 [thread overview]
Message-ID: <4FFAEB4F.3050806@windriver.com> (raw)
In-Reply-To: <1341844076.8066.17.camel@ted>
On 7/9/12 9:27 AM, Richard Purdie wrote:
> On Mon, 2012-07-09 at 07:16 -0700, Khem Raj wrote:
>> 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
>
> Our default CCACHE_DIR defined above this has ${PN} in it so just the
> package you are cleaning.
I'm worried about what happens if someone changes the CCACHE_DIR to a single
shared location.
--Mark
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-07-09 14:42 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
2012-07-09 14:27 ` Richard Purdie
2012-07-09 14:31 ` Mark Hatle [this message]
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=4FFAEB4F.3050806@windriver.com \
--to=mark.hatle@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.