From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Subject: Re: is it "addtask do_X ..." or "addtask X ..." or does it matter?
Date: Sat, 12 Jul 2014 16:25:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407121623480.27064@localhost> (raw)
In-Reply-To: <CABcZANkY6NJLP=YVJj1YM5LJ89MUtENCV9PMwKa2CKhr_NzmgQ@mail.gmail.com>
On Sat, 12 Jul 2014, Christopher Larson wrote:
> On Sat, Jul 12, 2014 at 4:22 AM, Robert P. J. Day <rpjday@crashcourse.ca>
> wrote:
>
> > want to clarify the two different ways to use addtask. for example:
> >
> > classes/kernel.bbclass:addtask savedefconfig after do_configure
> > classes/kernel.bbclass:addtask do_strip before do_sizecheck after
> > do_kernel_link_vmlinux
> > classes/kernel.bbclass:addtask sizecheck before do_install after do_strip
> >
> > so what is the preferred form? are they equivalent?
> >
>
> addtask do_strip will add a task named 'do_do_strip', afaik.
well, there is definitely some of that happening in the oe-core
codebase, feel free to:
$ grep -r "addtask do_" *
so i'm not sure what to make of that.
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-12 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 11:22 is it "addtask do_X ..." or "addtask X ..." or does it matter? Robert P. J. Day
2014-07-12 20:08 ` Christopher Larson
2014-07-12 20:25 ` Robert P. J. Day [this message]
2014-07-14 10:11 ` Robert P. J. Day
2014-07-15 0:41 ` Christopher Larson
2014-07-15 0:47 ` Robert P. J. Day
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.1407121623480.27064@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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 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.