bitbake user manual: shouldn't "Events" mention "[eventmask]"?

bitbake user manual: shouldn't "Events" mention "[eventmask]"?

[Robert P. J. Day]

  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?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: bitbake user manual: shouldn't "Events" mention "[eventmask]"?

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

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.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 1445 bytes --]

Re: bitbake user manual: shouldn't "Events" mention "[eventmask]"?

[Robert P. J. Day]

[-- 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
========================================================================

Re: bitbake user manual: shouldn't "Events" mention "[eventmask]"?

[Rifenbark, Scott M]

Hi, 

I updated the BB manual here to account for this flag.  Check it out and let me know if this adequately covers this issue:

http://www.yoctoproject.org/docs/1.7/bitbake-user-manual/bitbake-user-manual.html#events

Thanks, 
Scott

>-----Original Message-----
>From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
>devel-bounces@lists.openembedded.org] On Behalf Of Robert P. J. Day
>Sent: Monday, August 11, 2014 10:27 AM
>To: Christopher Larson
>Cc: BitBake developer list
>Subject: Re: [bitbake-devel] bitbake user manual: shouldn't "Events" mention
>"[eventmask]"?
>
>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
>===========================================================
>=============