Richard Purdie
<[email protected]>
writes:
>> ccache checks for existence of environment; not for its value:
>> ...
>> Hence, avoid setting of $CCACHE_DISABLE instead of assigning '0'.
>
> Why doesn't CCACHE_DISABLE[unexport] = "1" help here?
You mean, keeping the
| export CCACHE_DISABLE ??= "${@[0,1][d.getVar('CCACHE', True) == '']}"
and requesting explicitly that user specifies
| CCACHE_DISABLE[unexport] = "1"
in his .conf? Sounds hacky and inconsistent and makes it impossible to
set CCACHE_DISABLE by external environment.
> Doesn't the unexport flag stop this entering the environment?
Perhaps. In the current bitbake, 'unexport' takes precedence over
'export'. But is this specified somewhere and will perhaps be changed
in a later version.
Enrico
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
