aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChris Larson <chris_larson@mentor.com>2010-04-08 16:30:52 -0700
committerChris Larson <chris_larson@mentor.com>2010-04-09 12:49:22 -0700
commited35b30f8e09b0bfc15102fa6483c55d6b7d61de (patch)
treedc016fb0e34462658108e1d383cf2385da59c26a /doc
parent47449b2fc433e5725839ca4f7e9bca931a475838 (diff)
downloadbitbake-ed35b30f8e09b0bfc15102fa6483c55d6b7d61de.tar.gz
bb.event: NotHandled and Handled are on the way out
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/usermanual.xml4
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/manual/usermanual.xml b/doc/manual/usermanual.xml
index 6424a7ebd..bd44a69e3 100644
--- a/doc/manual/usermanual.xml
+++ b/doc/manual/usermanual.xml
@@ -215,13 +215,11 @@ addtask printdate before do_build</screen></para>
<para>BitBake allows to install event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure.</para>
<para><screen>addhandler myclass_eventhandler
python myclass_eventhandler() {
- from bb.event import NotHandled, getName
+ from bb.event import getName
from bb import data
print "The name of the Event is %s" % getName(e)
print "The file we run for is %s" % data.getVar('FILE', e.data, True)
-
- return NotHandled
}
</screen></para><para>
This event handler gets called every time an event is triggered. A global variable <varname>e</varname> is defined. <varname>e</varname>.data contains an instance of bb.data. With the getName(<varname>e</varname>)