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>
This commit is contained in:
parent
7ff22fc572
commit
ca85107b9a
|
@ -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>
|
||||
|
||||
|
|
Loading…
Reference in New Issue