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>
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate
Date: Mon, 14 May 2012 06:18:27 -0500	[thread overview]
Message-ID: <4FB0EA03.4040406@windriver.com> (raw)
In-Reply-To: <CABcZANnvJHzuTb7UTXAXvFzbHjWxAzoJNwvWp_zaeoNK3-z07Q@mail.gmail.com>

On 05/13/2012 09:47 PM, Chris Larson wrote:
> On Sun, May 13, 2012 at 7:28 PM, Jason Wessel
> <jason.wessel@windriver.com> wrote:
>> I am not exactly sure how to fix this, so I thought I might ask in the
>> form of a working patch.  The problem is that I want to use an
>> external CCACHE_DIR on some build servers, but use the defaults on
>> others.  Ultimately the sstate sums should be the same in either case,
>> but they are not due to the way that bitbake tracks the "export"
>> variables for inclusion i the sum dependencies.  My example test is to
>> simply set CCACHE_DIR = "/tmp/ccache" in the local.conf and recompile
>> the quilt-native package.
>>
>> I ended up adding another check to the dependency generator because
>> simply trying to use "unexport" had undesired effects.  If there is a
>> better or correct way of fixing this such that CCACHE_DIR will not
>> impact the sstate sum, I would really like to know how to do this. :-)
> 
> Add it to BB_HASHBASE_WHITELIST next to other variables like TMPDIR,
> FILE, and BBPATH.


Many thanks for the response, this definitely works for the CCACHE_DIR case.

I do have a question however.  With the patch I had created I was also able to add new exported variables to the local.conf like CCACHE_DISABLE on demand  Example:

export CCACHE_DISABLE = "1"
CCACHE_DISABLE[undep] = "1"

I would like to be able to do the same thing with the BB_HASHBASE_WHITELIST, like:

export CCACHE_DISABLE = "1"
BB_HASHBASE_WHITELIST += "CCACHE_DISABLE"

My question is if it would be ok to move the hashbase setup above all the requires *.conf lines such that this possible?

Thanks,
Jason.



  reply	other threads:[~2012-05-14 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  2:28 [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate Jason Wessel
2012-05-14  2:28 ` [PATCH 1/2] bitbake/lib/bb/data.py: Allow an exported variable to be excluded from dependency processing Jason Wessel
2012-05-14  2:28 ` [PATCH 2/2] bitbake.conf: A change to CCACHE_DIR should not change the sstate sum Jason Wessel
2012-05-14  2:47 ` [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate Chris Larson
2012-05-14 11:18   ` Jason Wessel [this message]
2012-05-14 21:33 ` Khem Raj
2012-05-14 21:50   ` Jason Wessel
2012-05-14 22:34     ` Khem Raj

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=4FB0EA03.4040406@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=clarson@kergoth.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