Bug 10682 - multiconfig sstate optimisations
Summary: multiconfig sstate optimisations
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: High enhancement
Target Milestone: 4.99
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-16 13:08 UTC by Richard Purdie
Modified: 2019-07-25 14:41 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.