[OE-core] [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate
Jason Wessel
jason.wessel at windriver.com
Mon May 14 11:18:27 UTC 2012
On 05/13/2012 09:47 PM, Chris Larson wrote:
> On Sun, May 13, 2012 at 7:28 PM, Jason Wessel
> <jason.wessel at 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.
More information about the Openembedded-core
mailing list