aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-10-03 10:02:05 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-10-11 08:51:21 +0100
commitca85107b9ad5358573052b88e98665c7110288c2 (patch)
treed62f3c53bb50c0a5dc86eb9d2bc1d42bf7971bc8 /documentation/ref-manual
parent7ff22fc572aec5900e8b7eb061ce31c3855b8fbd (diff)
downloadopenembedded-core-contrib-ca85107b9ad5358573052b88e98665c7110288c2.tar.gz
ref-manual: Updated build/tmp/cache/ reference section
Fixes [YOCTO #10356] Expanded the general description of this directory. (From yocto-docs rev: df71fe472f9d5cb5f809706ec4218952a49d31d3) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/ref-structure.xml18
1 files changed, 15 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index 6912d3f6b2..541a47e556 100644
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -660,9 +660,21 @@
<title><filename>build/tmp/cache/</filename></title>
<para>
- When BitBake parses the metadata, it creates a cache file of the result that can
- be used when subsequently running commands.
- BitBake stores these results here on a per-machine basis.
+ When BitBake parses the metadata (recipes and configuration files),
+ it caches the results in <filename>build/tmp/cache/</filename>
+ to speed up future builds.
+ The results are stored on a per-machine basis.
+ </para>
+
+ <para>
+ During subsequent builds, BitBake checks each recipe (together
+ with, for example, any files included or appended to it) to see
+ if they have been modified.
+ Changes can be detected, for example, through file modification
+ time (mtime) changes and hashing of file contents.
+ If no changes to the file are detected, then the parsed result
+ stored in the cache is reused.
+ If the file has changed, it is reparsed.
</para>
</section>