10356 2016-09-30 20:16:51 +0000 Suggested addition to explain how the recipe cache works 2016-10-03 19:32:19 +0000 1 1 9 Documentation Reference handbook 2.2 x86 Multiple RESOLVED FIXED 03 Oct 2016: RESOLVED Undecided normal 2.2 M4 1 ulfalizer srifenbark poky.doc.watcher poky.watcher srifenbark --- --- Done (doc changes complete) oldest_to_newest 66775 0 ulfalizer 2016-09-30 20:16:51 +0000 This was another dark corner for me. At a high level, it doesn't seem to be too bad. I suggest replacing '6.2.9. build/tmp/cache/' with the following: When BitBake parses the metadata (recipes and configuration files), it caches the results in build/tmp/cache/ to speed up future builds. The results are stored on a per-machine basis. During subsequent builds, BitBake checks each recipe (together with, for example, any files included or appended to it) to see if it has been modified. Changes can be detected, for example, through 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. Cheers, Ulf 66817 1 srifenbark 2016-10-03 17:04:17 +0000 Ulf, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#structure-build-tmp-cache. Let me know. Thanks, Scott 66828 2 ulfalizer 2016-10-03 18:12:35 +0000 Looks good! Thanks, Ulf 66835 3 srifenbark 2016-10-03 19:32:19 +0000 Thanks, Setting to RESOLVED and putting the doc flag to "done." scott