summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/event.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2017-07-06 12:53:33 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-07-08 13:29:54 +0100
commitbca4396106a51c7eba1da5fcbaba5e4e4964ca91 (patch)
tree95433a53454f13095c3926446ea4b68587467ad5 /bitbake/lib/bb/event.py
parent754c03006943a219ffd417c36ab909b464f57f67 (diff)
downloadopenembedded-core-contrib-bca4396106a51c7eba1da5fcbaba5e4e4964ca91.tar.gz
bitbake: bitbake: Add MultiConfigParsed event
There are some cases where the metadata needs to be aware a multiconfig build is happening and have access to the multiconfig data stores to merge data into the common build. This adds such an event allowing access to these datastores. (Bitbake rev: 160e47f5df90850e64dcb857c81a5039abc9235f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/event.py')
-rw-r--r--bitbake/lib/bb/event.py6
1 files changed, 6 insertions, 0 deletions
diff --git a/bitbake/lib/bb/event.py b/bitbake/lib/bb/event.py
index 6ccd4bdc38..1462382f10 100644
--- a/bitbake/lib/bb/event.py
+++ b/bitbake/lib/bb/event.py
@@ -358,6 +358,12 @@ class OperationProgress(Event):
class ConfigParsed(Event):
"""Configuration Parsing Complete"""
+class MultiConfigParsed(Event):
+ """Multi-Config Parsing Complete"""
+ def __init__(self, mcdata):
+ self.mcdata = mcdata
+ Event.__init__(self)
+
class RecipeEvent(Event):
def __init__(self, fn):
self.fn = fn