sstatesig: include native/cross/nativesdk deps in target signatures
* I don't have any real evidence or good statistics for this, but when
comparing signature dumps from my big bitbake world builds I usually
see a lot of rebuilds caused by changes in .bbclasses and only very
rare would be the case where oe-core upgrade brings changes in -native
recipes and no change in .bbclasses used from target recipes
* changing the default to include them shouldn't cause significant
increase in rebuilds and sstate reuse a bit safer
* people working on toolchain (e.g. using gcc from AUTOREV) can easily
extend sstate_rundepfilter to ignore them again (it's easier than
removing existing filter), example how add own signature handler in
your layer is here:
9ac3a7c803
(From OE-Core rev: 336a7897e39b9e42dcfcba9e2520ea96b0c6a8d6)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
b908caca1a
commit
9abc0028fc
|
@ -36,10 +36,6 @@ def sstate_rundepfilter(siggen, fn, recipename, task, dep, depname, dataCache):
|
|||
if isPackageGroup(fn):
|
||||
return False
|
||||
|
||||
# Drop native/cross/nativesdk dependencies from target recipes
|
||||
if isNative(depname) or isCross(depname) or isNativeSDK(depname):
|
||||
return False
|
||||
|
||||
# Exclude well defined machine specific configurations which don't change ABI
|
||||
if depname in siggen.abisaferecipes and not isImage(fn):
|
||||
return False
|
||||
|
|
Loading…
Reference in New Issue