All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 27 Jul 2014 08:10:22 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407270804480.4789@localhost> (raw)
In-Reply-To: <CABcZANmro1OOnNZjAM-mkPjxV7wTUOpKHR9AQrqJTMhV5LOs5g@mail.gmail.com>

On Sat, 26 Jul 2014, Christopher Larson wrote:

> On Sat, Jul 26, 2014 at 5:43 AM, Robert P. J. Day <rpjday@crashcourse.ca>
> wrote:
>
> > 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.
>
> Good question, I have no idea :) Clearly it should be somewhere.

  actually, while i'm there:

http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#variable-flags

anything else i should add just to make it a single patch? (yes, i
realize this should have gone to the bitbake list at this point but
let's just finish it off here and be done with it.)

  it occurs that one could mention variable flags like [doc] in that
section since, technically, that section is entitled "Variable Flags",
not just "Task Flags", even though it is clearly discussing only task
flags, which seems a touch incomplete.

  and just so i'm clear on this, one does not need to pre-declare
variable flags anywhere, right? one can just start using them, yes?
that's probably worth mentioning as well as, on a regular basis, my
students ask, "where do i declare that thing that looks like a
subscript?"

  anyway, any suggestions as to what else can go in there while i
ponder what to add/change?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



      parent reply	other threads:[~2014-07-27 12:10 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
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 [this message]

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.1407270804480.4789@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.