* parse does not cache
@ 2013-02-23 21:44 Andreas Müller
2013-02-24 0:48 ` Jason Wessel
0 siblings, 1 reply; 3+ messages in thread
From: Andreas Müller @ 2013-02-23 21:44 UTC (permalink / raw)
To: bitbake-devel
Hi,
with the latest HEAD bitbake performs a full parse for every run. I
could not find a hint so far - so is it a bug or did I miss something?
Andreas
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: parse does not cache
2013-02-23 21:44 parse does not cache Andreas Müller
@ 2013-02-24 0:48 ` Jason Wessel
2013-02-24 10:20 ` Andreas Müller
0 siblings, 1 reply; 3+ messages in thread
From: Jason Wessel @ 2013-02-24 0:48 UTC (permalink / raw)
To: Andreas Müller; +Cc: bitbake-devel
On 02/23/2013 03:44 PM, Andreas Müller wrote:
> Hi,
>
> with the latest HEAD bitbake performs a full parse for every run. I
> could not find a hint so far - so is it a bug or did I miss something?
It depends on what OE you are using. If you don't have the changes for the BB_ORIGENV introduced by commit 0a99563a4ea270594fd9a61da46f9387fb79dc66 you will find that things definitely always parse every single time.
You can always try reverting that single commit to see if the behavior changes. There are also other changes like that with in the bitbake history where it does not always work with older versions of OE.
Cheers,
Jason.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: parse does not cache
2013-02-24 0:48 ` Jason Wessel
@ 2013-02-24 10:20 ` Andreas Müller
0 siblings, 0 replies; 3+ messages in thread
From: Andreas Müller @ 2013-02-24 10:20 UTC (permalink / raw)
To: Jason Wessel; +Cc: bitbake-devel
On Sun, Feb 24, 2013 at 1:48 AM, Jason Wessel
<jason.wessel@windriver.com> wrote:
> On 02/23/2013 03:44 PM, Andreas Müller wrote:
>> Hi,
>>
>> with the latest HEAD bitbake performs a full parse for every run. I
>> could not find a hint so far - so is it a bug or did I miss something?
>
> It depends on what OE you are using. If you don't have the changes for the BB_ORIGENV introduced by commit 0a99563a4ea270594fd9a61da46f9387fb79dc66 you will find that things definitely always parse every single time.
>
> You can always try reverting that single commit to see if the behavior changes. There are also other changes like that with in the bitbake history where it does not always work with older versions of OE.
>
> Cheers,
> Jason.
You are right - reverting 0a99563a4ea270594fd9a61da46f9387fb79dc66
helps. Seems my OE does not match bitbake HEAD.
Thanks
Andreas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-02-24 10:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-23 21:44 parse does not cache Andreas Müller
2013-02-24 0:48 ` Jason Wessel
2013-02-24 10:20 ` Andreas Müller
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.