| Message ID | 20221211172557.21956-1-richard.purdie@linuxfoundation.org |
|---|---|
| State | Accepted, archived |
| Commit | 6b213590ed0e77683cf7fbce6bbe9605ddecf3d3 |
| Headers | show |
| Series | [1/4] siggen: Directly store datacaches reference | expand |
diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py index 63cce8184f..991aa94f67 100644 --- a/lib/bb/runqueue.py +++ b/lib/bb/runqueue.py @@ -651,6 +651,8 @@ class RunQueueData: # Nothing to do return 0 + bb.parse.siggen.setup_datacache(self.dataCaches) + self.init_progress_reporter.start() self.init_progress_reporter.next_stage() diff --git a/lib/bb/siggen.py b/lib/bb/siggen.py index cdf7d03a34..e57f1ffe69 100644 --- a/lib/bb/siggen.py +++ b/lib/bb/siggen.py @@ -70,6 +70,9 @@ class SignatureGenerator(object): def postparsing_clean_cache(self): return + def setup_datacache(self, datacaches): + self.datacaches = datacaches + def get_unihash(self, tid): return self.taskhash[tid]
It is becomming clear the siggen needs access to our cache data but we can't always obtain it in the contexts we need to. Add it directly, meaning over time we should be able to simplify the APIs and stop convoluting new ones! Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- lib/bb/runqueue.py | 2 ++ lib/bb/siggen.py | 3 +++ 2 files changed, 5 insertions(+)