Bug 12157 - Avoid rebuilds when recipe specific sysroot has not changed
Summary: Avoid rebuilds when recipe specific sysroot has not changed
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-10-03 08:19 UTC by Ola Nilsson
Modified: 2019-10-03 15:33 UTC (History)
3 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 Ola Nilsson 2017-10-03 08:19:02 UTC 
Many packages such as libraries, kernel modules, and the kernel itself can trigger many rebuilds of other packages even when they are not needed.  

A shared library that is rebuilt but has no interface changes will trigger rebuilds on all recipes that DEPENDS on it, even if it is not really needed.  

Could the populate_sysroot task somehow check a hash of the exported files to see whether dependent packages really need to rebuild?
Comment 1 Richard Purdie 2019-10-03 15:33:01 UTC 
We now have the hash equivalency server which addresses this problem.