d0c615e51e
The bitbake wrapper script is set up such that the -p (--parse-only) command line option is not executed under pseudo, and it sets the PSEUDO_BUILD variable to indicate whether or not pseudo is being used. Since PSEUDO_BUILD is allowed through into the environment via BB_ENV_EXTRAWHITE it influences the data hash and thus if you run "bitbake -p" and then run bitbake again to actually build something, the change to PSEUDO_BUILD causes the cache from the -p execution not to be used. This is fixed simply by adding PSEUDO_BUILD to BB_HASHCONFIG_WHITELIST in bitbake.conf so that it doesn't influence the data hash. Fixes [YOCTO #2600]. (From OE-Core rev: 1e50225df2d6b5f10c5648703282235a11b1efb3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
|---|---|---|
| .. | ||
| distro | ||
| machine | ||
| machine-sdk | ||
| swabber | ||
| abi_version.conf | ||
| bitbake.conf | ||
| documentation.conf | ||
| layer.conf | ||
| licenses.conf | ||
| multilib.conf | ||
| prexport.conf | ||
| primport.conf | ||
| sanity.conf | ||