summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/event.py
diff options
context:
space:
mode:
authorElliot Smith <elliot.smith@intel.com>2016-07-11 16:23:05 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-08-11 00:09:26 +0100
commitc471740f5ba023dccc992438c75f1534950d26af (patch)
tree764bf652494355fc87e0a186414a23e9dfefd88f /bitbake/lib/bb/event.py
parentf4e65d1cd0ee4e847d286aa88639d7aac5bff094 (diff)
downloadpoky-c471740f5ba023dccc992438c75f1534950d26af.tar.gz
bitbake: cooker: add BuildInit event
In situations where a bitbake run fails before the build properly starts and BuildStarted is fired, a UI has no way to get at the targets passed to the build. This makes it difficult for the UI to report on the targets which failed. Fire a BuildInit event before running buildTargets() or buildFile(). This enables a UI to capture targets passed to buildTargets(), even if the build fails (e.g. the targets themselves are invalid). [YOCTO #8440] (Bitbake rev: ac02fda870965bf7d44ff5688eda54d2d11ab9c7) Signed-off-by: Elliot Smith <elliot.smith@intel.com> 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, 5 insertions, 1 deletions
diff --git a/bitbake/lib/bb/event.py b/bitbake/lib/bb/event.py
index a5f026e151..1f3200e196 100644
--- a/bitbake/lib/bb/event.py
+++ b/bitbake/lib/bb/event.py
@@ -382,7 +382,11 @@ class BuildBase(Event):
382 382
383 383
384 384
385 385class BuildInit(BuildBase):
386 """buildFile or buildTargets was invoked"""
387 def __init__(self, p=[]):
388 name = None
389 BuildBase.__init__(self, name, p)
386 390
387class BuildStarted(BuildBase, OperationStarted): 391class BuildStarted(BuildBase, OperationStarted):
388 """bbmake build run started""" 392 """bbmake build run started"""