| Message ID | 20230110160237.1470090-1-richard.purdie@linuxfoundation.org |
|---|---|
| State | Accepted, archived |
| Commit | db743cc78fe5172bb4a4dac9c1dad4f5aa9e1491 |
| Headers | show |
| Series | uninative: Ensure uninative is enabled in all cases for BuildStarted event | expand |
diff --git a/meta/classes-global/uninative.bbclass b/meta/classes-global/uninative.bbclass index 42c5f8fdf2e..366f7ac7935 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
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 <richard.purdie@linuxfoundation.org> --- meta/classes-global/uninative.bbclass | 2 ++ 1 file changed, 2 insertions(+)