summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/user-manual/user-manual-ref-variables.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-02-25 17:56:24 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-09 18:59:04 -0700
commitc5095104aaf28e11b508faa59ca71d233123a6d8 (patch)
treef8c462983ad7df9e535cb222f3b79a6bdf4ca6b5 /bitbake/doc/user-manual/user-manual-ref-variables.xml
parent4cd882b9d05f503ee58f78cceebaa9e63dc2048f (diff)
downloadpoky-c5095104aaf28e11b508faa59ca71d233123a6d8.tar.gz
bitbake: user-manual: Review edits from Richard (second draft)
Applied the comprehensive set of review comments from Richard Purdie. All files affected. One major point here was that the "BitBake Command" chapter was eliminated. This information was folded into various areas of the book. Consequently, the bits including the file for make had to be updated. (Bitbake rev: 8ec38c6b456a92a0e0b9b04c2793a5b148be5027) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc/user-manual/user-manual-ref-variables.xml')
-rw-r--r--bitbake/doc/user-manual/user-manual-ref-variables.xml9
1 files changed, 4 insertions, 5 deletions
diff --git a/bitbake/doc/user-manual/user-manual-ref-variables.xml b/bitbake/doc/user-manual/user-manual-ref-variables.xml
index e1bf2b561d..ff2d59a6e6 100644
--- a/bitbake/doc/user-manual/user-manual-ref-variables.xml
+++ b/bitbake/doc/user-manual/user-manual-ref-variables.xml
@@ -388,16 +388,15 @@
388 <glossentry id='var-BB_HASHCONFIG_WHITELIST'><glossterm>BB_HASHCONFIG_WHITELIST</glossterm> 388 <glossentry id='var-BB_HASHCONFIG_WHITELIST'><glossterm>BB_HASHCONFIG_WHITELIST</glossterm>
389 <glossdef> 389 <glossdef>
390 <para> 390 <para>
391 Lists variables that are excluded from checksum 391 Lists variables that are excluded from base configuration
392 comparisons to determine if the cache can be reused. 392 checksum, which is used to determine if the cache can
393 be reused.
393 </para> 394 </para>
394 395
395 <para> 396 <para>
396 One of the ways BitBake determines whether to re-parse the 397 One of the ways BitBake determines whether to re-parse the
397 main metadata is through checksums of the variables in the 398 main metadata is through checksums of the variables in the
398 datastore of the base configuration data (see the 399 datastore of the base configuration data.
399 <link linkend='var-BB_HASHBASE_WHITELIST'><filename>BB_HASHBASE_WHITELIST</filename></link>
400 variable).
401 There are variables that you typically want to exclude when 400 There are variables that you typically want to exclude when
402 checking whether or not to re-parse and thus rebuild the 401 checking whether or not to re-parse and thus rebuild the
403 cache. 402 cache.