Bug 10682

Summary: multiconfig sstate optimisations
Product: [Build System, Metadata & Runtime] BitBake Reporter: Richard Purdie <richard.purdie>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: High CC: JPEWhacker, patrick.ohly, poky.bs.watcher, poky.watcher, randy.macleod
Version: 2.3   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Richard Purdie 2016-11-16 13:08:51 UTC 
Right now, if you have a mutliconfig build and which is configured for two different TMPDIRs yet they share sstate objects, they will just build them in parallel and not reuse the data unless it was generated before the build.

Fixing this is hard as sstate runs as a separate task at the start of the process however this bug is to track that issue and see if there are ways we could enable sstate reuse in such cases.

Its related to the problem that if sstate appears in the sstate cache half way through a build, it also won't get reused. It may not be possible to solve this easily without changes that would be too invasive.