All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] externalsrc: Use deltask API
Date: Sat, 21 Dec 2013 09:01:26 +0000	[thread overview]
Message-ID: <1387616486.6402.114.camel@ted> (raw)
In-Reply-To: <CANyK_8eHa5N-W6t07mGuyyuLgHj0CdUw8n9ivA14+h5VpLR0rA@mail.gmail.com>

On Fri, 2013-12-20 at 18:24 +0000, Paul Barker wrote:
> On 18 December 2013 11:30, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Now we have deltask API, stop poking around bitbake internal variables.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
> > index c759289..53c71cb 100644
> > --- a/meta/classes/externalsrc.bbclass
> > +++ b/meta/classes/externalsrc.bbclass
> > @@ -26,21 +26,6 @@
> >
> >  SRCTREECOVEREDTASKS ?= "do_patch do_unpack do_fetch"
> >
> > -def remove_tasks(tasks, deltasks, d):
> > -    for task in tasks:
> > -        deps = d.getVarFlag(task, "deps")
> > -        for preptask in deltasks:
> > -            if preptask in deps:
> > -                deps.remove(preptask)
> > -        d.setVarFlag(task, "deps", deps)
> > -    # Poking around bitbake internal variables is evil but there appears to be no better way :(
> > -    tasklist = d.getVar('__BBTASKS') or []
> > -    for task in deltasks:
> > -        d.delVarFlag(task, "task")
> > -        if task in tasklist:
> > -            tasklist.remove(task)
> > -    d.setVar('__BBTASKS', tasklist)
> > -
> >  python () {
> >      externalsrc = d.getVar('EXTERNALSRC', True)
> >      if externalsrc:
> > @@ -53,16 +38,16 @@ python () {
> >          d.setVar('SRC_URI', '')
> >
> >          tasks = filter(lambda k: d.getVarFlag(k, "task"), d.keys())
> > -        covered = d.getVar("SRCTREECOVEREDTASKS", True).split()
> >
> >          for task in tasks:
> >              if task.endswith("_setscene"):
> >                  # sstate is never going to work for external source trees, disable it
> > -                covered.append(task)
> > +                bb.build.deltask(task, d)
> >              else:
> >                  # Since configure will likely touch ${S}, ensure only we lock so one task has access at a time
> >                  d.appendVarFlag(task, "lockfiles", "${S}/singletask.lock")
> >
> > -        remove_tasks(tasks, covered, d)
> > +        for task in covered:
> > +            bb.build.deltask(task, d)
> >  }
> >
> 
> I've just updated oe-core whilst trying to test my in-development
> version of opkg using externalsrc and I'm getting:
> 
>  *** 0022:        for task in covered:
>      0023:            bb.build.deltask(task, d)
>      0024:
> Exception: NameError: global name 'covered' is not defined
> 
> I don't really know the code in question well so I don't know whether
> the solution is to remove that last for loop or to add back in the
> declaration of 'covered'.

Sorry about that, I think I've mixed up some patches. I've pushed
something which should fix it.

Cheers,

Richard




      reply	other threads:[~2013-12-21  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 11:30 [PATCH] externalsrc: Use deltask API Richard Purdie
2013-12-20 18:24 ` Paul Barker
2013-12-21  9:01   ` Richard Purdie [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=1387616486.6402.114.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    /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.