Hash Equivalence is an extremely powerful feature for reducing build time. In simple terms, if something is rebuilt and the output is the same as a previous build, all sstate build artefacts beyond that point can be reused instead of being rebuilt.
This can be done with a local hash equivalence database/server which is the default and even local builds with a local sstate can benefit hugely from it. There is an assumption that builds are reproducible in order for this to work optimally. The downside is that when enabled to pull from a shared sstate cache, you need to use a common hash equivalence server to match it for things to work well. OE-Core wasn't enabling hash equivalence by default but this changes it to do so. This has been extensively tested as the deafault in Poky for a long time. Signed-off-by: Richard Purdie <[email protected]> --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index d247eb3adfc..9308ee431f2 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -951,7 +951,7 @@ BB_DEFAULT_EVENTLOG ?= "${LOG_DIR}/eventlog/${DATETIME}.json" BB_DEFER_BBCLASSES = "native nativesdk cross crosssdk" # Setup our default hash policy -BB_SIGNATURE_HANDLER ?= "OEBasicHash" +BB_SIGNATURE_HANDLER ?= "OEEquivHash" BB_HASHEXCLUDE_COMMON ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH BBSERVER DL_DIR \ THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL \ USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE PRSERV_HOST \
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#232001): https://lists.openembedded.org/g/openembedded-core/message/232001 Mute This Topic: https://lists.openembedded.org/mt/118010453/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
