From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Subject: Re: i'm assuming some "do_<task>[dirs] =" directives are redundant, yes?
Date: Sat, 26 Jul 2014 08:43:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407260841510.28771@localhost> (raw)
In-Reply-To: <CABcZANkamKKfYkMBnit4H8go-_BY_0ePWbg32Fx6oCjNVspiwg@mail.gmail.com>
On Mon, 21 Jul 2014, Christopher Larson wrote:
> On Mon, Jul 21, 2014 at 2:59 AM, Robert P. J. Day <rpjday@crashcourse.ca>
> wrote:
>
> >
> > pedantic observation -- i notice in base.bbclass:
> >
> > do_unpack[dirs] = "${WORKDIR}"
> >
> > and over in patch.bbclass:
> >
> > addtask patch after do_unpack
> > do_patch[dirs] = "${WORKDIR}"
> >
> > so given that patching has been added as a task after unpacking,
> > wouldn't ${WORKDIR} already be guaranteed to exist? doesn't hurt, of
> > course, and no, i have no intention of trying to clean any of that up
> > :-), i just wanted to clarify the actual mechanics.
>
>
> 'dirs' isn't just a list of dirs to create, it also sets the current
> working directory for the task. The last directory listed is where
> the path is set.
is that documented anywhere? the "variable flags" section of the
bitbake user manual says nothing about that last obviously significant
property.
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-26 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 9:59 i'm assuming some "do_<task>[dirs] =" directives are redundant, yes? Robert P. J. Day
2014-07-21 15:27 ` Christopher Larson
2014-07-26 12:43 ` Robert P. J. Day [this message]
2014-07-26 23:13 ` Christopher Larson
2014-07-27 11:54 ` Robert P. J. Day
2014-07-27 12:10 ` 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.1407260841510.28771@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox