From 8e7e050bce75008cf91fc3d13be72be730f71c7b Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Tue, 10 Jan 2023 16:00:18 +0000 Subject: uninative: Ensure uninative is enabled in all cases for BuildStarted event Recent changes in bitbake mean the datastore is not always reset between ConfigParsed and BuildStarted. This means in a fresh buiild, with memory resident bitbake active, uninative may end up disabled. Update the code so the enable code is always run at BuildStarted if needed. (From OE-Core rev: db743cc78fe5172bb4a4dac9c1dad4f5aa9e1491) Signed-off-by: Richard Purdie --- meta/classes-global/uninative.bbclass | 2 ++ 1 file changed, 2 insertions(+) (limited to 'meta/classes-global/uninative.bbclass') diff --git a/meta/classes-global/uninative.bbclass b/meta/classes-global/uninative.bbclass index 42c5f8fdf2..366f7ac793 100644 --- a/meta/classes-global/uninative.bbclass +++ b/meta/classes-global/uninative.bbclass @@ -40,6 +40,8 @@ python uninative_event_fetchloader() { with open(loaderchksum, "r") as f: readchksum = f.read().strip() if readchksum == chksum: + if "uninative" not in d.getVar("SSTATEPOSTUNPACKFUNCS"): + enable_uninative(d) return import subprocess -- cgit v1.2.3-54-g00ecf