Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables
Date: Mon, 14 May 2012 11:49:12 -0500	[thread overview]
Message-ID: <4FB13788.2020200@windriver.com> (raw)
In-Reply-To: <1337011770-24297-1-git-send-email-jason.wessel@windriver.com>

On 05/14/2012 11:09 AM, Jason Wessel wrote:
> The end user of oe-core should be free to turn off ccache, or use an
> external ccache without impacting the sstate sums.
> 
> Example of using a different ccache directory via local.conf
> 
> CCACHE_DIR = "/tmp/ccache"
> 
> Example of turning off ccache:
> 
> export CCACHE_DISABLE = "1"
> BB_HASHBASE_WHITELIST += "CCACHE_DISABLE"


Oops.  I got this totally wrong...  It is bogus to move around the defaults in the core bitbake.conf.

All that needs to be done for the second case is to add to my local.conf:

export CCACHE_DISABLE = "1"
BB_HASHBASE_WHITELIST_append += "CCACHE_DISABLE"

And that doesn't require any changes to the bitbake.conf.

Sorry for the noise.   I'll send a patch just to add CCACHE_DIR to the BB_HASHBASE_WHITELIST.

Cheers,
Jason.





  parent reply	other threads:[~2012-05-14 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 16:09 [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables Jason Wessel
2012-05-14 16:09 ` [PATCH 1/2] bitbake.conf: Move default hash policy initialization before conf file inclusion Jason Wessel
2012-05-14 16:09 ` [PATCH 2/2] bitbake.conf: Add CCACHE_DIR to BB_HASHBASE_WHITELIST Jason Wessel
2012-05-14 16:49 ` Jason Wessel [this message]
2012-05-14 17:18 ` [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables Marko Lindqvist
2012-05-14 17:35   ` Chris Larson
2012-05-14 20:58   ` Jason Wessel
2012-05-14 22:00     ` Marko Lindqvist
2012-05-14 22:24       ` Jason Wessel

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=4FB13788.2020200@windriver.com \
    --to=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