Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ccache: Separate out into its own class
Date: Tue, 29 May 2012 13:48:31 +0100	[thread overview]
Message-ID: <1338295711.20169.106.camel@ted> (raw)
In-Reply-To: <4FC4C2D4.1090608@windriver.com>

On Tue, 2012-05-29 at 07:36 -0500, Jason Wessel wrote:
> On 05/29/2012 07:29 AM, Richard Purdie wrote:
> > Currently, ccache is used if it is present. When building from scratch it gives
> > no performance improvement and creates a ton of empty directories even when its
> > not in use.
> >
> > This change moves ccache support to a bbclass file which the user can choose to
> > enable. This should make builds more determinstic and make it easier/clearer
> > to the end user when its being used and when it is not.
> 
> Are the sstate sums the same with and without the use of the new bbclass ccache?
> 
> It is not clear to me that this is or is not the case based on this single commit header.

There is a problem with the existing sstate checksums since CCACHE
itself is not being excluded, only CCACHE_DIR so you'd end up with
sstate built using ccache and sstate built without using cccache with
different checksums. This change unifies those to have matching sstate
checksums.

So with and without use of the class, the checksums should now be the
same.

Cheers,

Richard




  reply	other threads:[~2012-05-29 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 12:29 [PATCH] ccache: Separate out into its own class Richard Purdie
2012-05-29 12:36 ` Jason Wessel
2012-05-29 12:48   ` Richard Purdie [this message]
2012-05-29 13:40 ` Enrico Scholz
2012-05-30  9:33   ` 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=1338295711.20169.106.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jason.wessel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox