From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: overriding tasks with EXPORT_FUNCTIONS
Date: Tue, 22 Jul 2014 09:22:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407220921230.4203@localhost> (raw)
In-Reply-To: <53CE64C9.2010402@linaro.org>
On Tue, 22 Jul 2014, Trevor Woerner wrote:
> On 07/14/14 08:26, Paul Eggleton wrote:
> > Unfortunately as far as the BitBake manual is concerned, it pretty
> > much has to be abstract. Remember that there are no base
> > implementations of any task functions in BitBake itself; the ones
> > you refer to are in OE's base.bbclass.
>
> In reality there are only about 2 people on the whole planet for
> whom that distinction is important :-)
i should point out that fetching is defined in bitbake, while
everything else is in oe-core. just being difficult. :-)
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-07-22 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 14:19 overriding tasks with EXPORT_FUNCTIONS Robert P. J. Day
2014-07-14 9:24 ` Paul Eggleton
2014-07-14 10:18 ` Robert P. J. Day
2014-07-14 10:22 ` Paul Eggleton
2014-07-14 12:20 ` Robert P. J. Day
2014-07-14 12:26 ` Paul Eggleton
2014-07-22 13:19 ` Trevor Woerner
2014-07-22 13:22 ` Robert P. J. Day [this message]
2014-07-22 13:42 ` Trevor Woerner
2014-07-22 13:40 ` Paul Eggleton
2014-07-14 12:30 ` Burton, Ross
2014-07-14 13:33 ` Robert P. J. Day
2014-07-14 15:19 ` Paul Eggleton
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.1407220921230.4203@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox