From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <clarson@kergoth.com>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: bitbake user manual: shouldn't "Events" mention "[eventmask]"?
Date: Mon, 11 Aug 2014 13:27:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408111320560.6960@localhost> (raw)
In-Reply-To: <CABcZANkvKtcEfNBHJ3VfDV_A61WZ6H=bm_MgtJ4EbPcRgOdW0w@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1410 bytes --]
On Mon, 11 Aug 2014, Christopher Larson wrote:
>
> On Mon, Aug 11, 2014 at 5:08 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> reading up on events in BB manual and section 3.7, "Events", talks
> of defining event handlers, but claims:
>
> "This event handler gets called every time an event is triggered."
>
> but don't you have to associate an event handler with one or more
> events using the "[eventmask]" flag? that seems like a fairly
> significant omission from that section. or am i just
> misunderstanding how events work?
>
> eventmask is a fairly recent addition. If eventmask is undefined,
> the handler is called for all events, and its left to the event
> handler to make sure it's only doing its logic for the right events
> (e.g. call isinstance() on 'e' to check what event it is). The docs
> likely were never updated to include it.
yeah, that's probably something that should be in the bitbake manual
somewhere. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-08-11 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 12:08 bitbake user manual: shouldn't "Events" mention "[eventmask]"? Robert P. J. Day
2014-08-11 15:06 ` Christopher Larson
2014-08-11 17:27 ` Robert P. J. Day [this message]
2014-08-13 13:18 ` Rifenbark, Scott M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.11.1408111320560.6960@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.