Bug 10356

Summary: Suggested addition to explain how the recipe cache works
Product: [Documentation] Reference Reporter: ulfalizer
Component: handbookAssignee: Scott Rifenbark <srifenbark>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: poky.doc.watcher, poky.watcher, srifenbark
Version: 2.2   
Target Milestone: 2.2 M4   
Hardware: x86   
OS: Multiple   
Whiteboard: 03 Oct 2016: RESOLVED
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

Description ulfalizer 2016-09-30 20:16:51 UTC
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
Comment 1 Scott Rifenbark 2016-10-03 17:04:17 UTC
Ulf, 

See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#structure-build-tmp-cache.  Let me know.

Thanks, 
Scott
Comment 2 ulfalizer 2016-10-03 18:12:35 UTC
Looks good!

Thanks,
Ulf
Comment 3 Scott Rifenbark 2016-10-03 19:32:19 UTC
Thanks, 

Setting to RESOLVED and putting the doc flag to "done."

scott