* [PATCH] runqueue: Add handling of virtual/xxx provider mappings
@ 2015-09-30 13:29 Richard Purdie
0 siblings, 0 replies; only message in thread
From: Richard Purdie @ 2015-09-30 13:29 UTC (permalink / raw)
To: bitbake-devel
This firstly prints debug messages which show how bitbake decided to resolve
the virtual/xxx providers which is useful for debugging.
If the siggen has a tasks_resolved() method, it calls this, passing in
the mappings, allowing that to do things with the resolved names.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index 49d853d..8370579 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -824,6 +824,15 @@ class RunQueueData:
st = "do_%s" % st
invalidate_task(fn, st, True)
+ # Create and print to the logs a virtual/xxxx -> PN (fn) table
+ virtmap = taskData.get_providermap()
+ virtpnmap = {}
+ for v in virtmap:
+ virtpnmap[v] = self.dataCache.pkg_fn[virtmap[v]]
+ bb.debug(2, "%s resolved to: %s (%s)" % (v, virtpnmap[v], virtmap[v]))
+ if hasattr(bb.parse.siggen, "tasks_resolved"):
+ bb.parse.siggen.tasks_resolved(virtmap, virtpnmap, self.dataCache)
+
# Iterate over the task list and call into the siggen code
dealtwith = set()
todeal = set(range(len(self.runq_fnid)))
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2015-09-30 13:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-30 13:29 [PATCH] runqueue: Add handling of virtual/xxx provider mappings Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox