All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: number of tasks increased since last update
Date: Wed, 1 Aug 2012 14:16:33 -0500	[thread overview]
Message-ID: <50198091.6050001@windriver.com> (raw)
In-Reply-To: <CABcZANk2SzKKcXTdU0MLUeXwOWSxq4HqJceMPO6tOLP3M_GejA@mail.gmail.com>

On 8/1/12 2:08 PM, Chris Larson wrote:
> On Wed, Aug 1, 2012 at 8:29 AM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
>> today I updated and found the the number of tasks has increased about
>> 400. Another strange behaviour: in my build dir there are two new
>> folders:
>>
>> x86_64-nativesdk-angstromsdk-linux
>> x86_64-angstromsdk-linux
>>
>> but up to now I was not interested in sdk stuff. Is that another bug
>> or a feature?
>
> I just went to build core-image-base and saw it building crosssdk
> stuff -- not sure if it's related, but thought I'd throw that
> datapoint out there.
>

do you have the updated bitbake?  Prior to RP's changes about a month ago, the 
task / dependency resolver was unable to resolve things on a per-task basis.  So 
any task within a recipe triggered the resolver to build dependencies.

The SDK stuff adds dependencies only do the sdk task.

With the current head of tree bitbake, I have not seen a revert of behavior... 
the SDK items only build when triggered.

--Mark



  reply	other threads:[~2012-08-01 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 15:29 number of tasks increased since last update Andreas Müller
2012-08-01 19:08 ` Chris Larson
2012-08-01 19:16   ` Mark Hatle [this message]
2012-08-01 20:06     ` Chris Larson
2012-08-01 20:55       ` Chris Larson
2012-08-01 19:17   ` Elvis Dowson
2012-08-01 21:06 ` Richard Purdie

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=50198091.6050001@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@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.