All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: overriding tasks with EXPORT_FUNCTIONS
Date: Mon, 14 Jul 2014 10:24:52 +0100	[thread overview]
Message-ID: <3072899.OS8yJTfGtp@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1407130915280.31826@localhost>

Hi Robert,

On Sunday 13 July 2014 10:19:08 Robert P. J. Day wrote:
>   followup to last post -- all of the methods for "overriding" task
> definitions in the last post can be used without predeclaring that
> you're about to do that; you just go ahead and do it in either a class
> file or a recipe file. on the other hand, EXPORT_FUNCTIONS allows you
> to retain the base definition of a task (or non-task function, as i
> read it), then define a more general enhanced version.
> 
>   (side note: i don't see a single mention of "EXPORT_FUNCTIONS" in
> any of the numerous yocto docs -- i think this feature needs some
> explanation *somewhere*. :-)

Did you try the new BitBake manual?

http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#flexible-inheritance-for-class-functions

Let me know if that doesn't answer your questions.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2014-07-14  9:25 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 [this message]
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
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=3072899.OS8yJTfGtp@peggleto-mobl5.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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.