From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: possible clarification of EXPORT_FUNCTIONS for user manual
Date: Wed, 9 Jul 2014 17:42:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407091742090.6258@localhost> (raw)
In-Reply-To: <1404941917.15985.63.camel@ted>
On Wed, 9 Jul 2014, Richard Purdie wrote:
> On Wed, 2014-07-09 at 11:14 -0400, Robert P. J. Day wrote:
> > so, just to make sure i'm understanding this correctly, in section
> > 3.4.5 of BB user manual, discussion of EXPORT_FUNCTIONS talks about
> > the general concept of exporting *functions*, but the entire section
> > uses exclusively "do_" examples, which might mislead the reader into
> > thinking it's good only for *tasks*.
> >
> > i decided to look through the oe-core layer for examples of
> > exporting an actual function, and i found all of one example -- in
> > meta/classes/debian.bbclass:
> >
> > python debian_package_name_hook () {
> > ... snip ...
> > }
> > ...
> > EXPORT_FUNCTIONS package_name_hook
> >
> > which seems like a valid example of exporting a function, except i
> > can't find a single example of this function being used anywhere else.
> > am i missing something?
> >
> > anyway, i guess my point is that that section could be tweaked to
> > emphasize that exporting works for both functions and tasks, although
> > the only function example i found seems unused. thoughts?
>
> package_name_hook is called by package.bbclass
whoops, quite so, not sure how i missed that.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-07-09 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:14 possible clarification of EXPORT_FUNCTIONS for user manual Robert P. J. Day
2014-07-09 21:38 ` Richard Purdie
2014-07-09 21:42 ` Robert P. J. Day [this message]
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.1407091742090.6258@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox