From: Richard Purdie <[email protected]> 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. Signed-off-by: Richard Purdie <[email protected]> (cherry picked from commit db743cc78fe5172bb4a4dac9c1dad4f5aa9e1491) Signed-off-by: Steve Sakoman <[email protected]> --- meta/classes/uninative.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass index 4412d7c567..2940935dd7 100644 --- a/meta/classes/uninative.bbclass +++ b/meta/classes/uninative.bbclass @@ -34,6 +34,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 -- 2.34.1
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#183252): https://lists.openembedded.org/g/openembedded-core/message/183252 Mute This Topic: https://lists.openembedded.org/mt/99700033/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
