All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: openembedded-devel@lists.openembedded.org,
	 Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: overriding tasks with EXPORT_FUNCTIONS
Date: Tue, 22 Jul 2014 09:19:05 -0400	[thread overview]
Message-ID: <53CE64C9.2010402@linaro.org> (raw)
In-Reply-To: <28111309.Fiim3rPSbe@peggleto-mobl5.ger.corp.intel.com>

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 :-)

For the rest of us, it would be nice if there was some middle ground
from which a document could be written that treated these two entities
as one; at least up until such a time as some other project comes along
and uses bitbake for something other than OE/Yocto :-D


  reply	other threads:[~2014-07-22 13:19 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 [this message]
2014-07-22 13:22         ` Robert P. J. Day
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=53CE64C9.2010402@linaro.org \
    --to=trevor.woerner@linaro.org \
    --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 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.