From: Jason Wessel <jason.wessel@windriver.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: parse does not cache
Date: Sat, 23 Feb 2013 18:48:42 -0600 [thread overview]
Message-ID: <5129636A.1070706@windriver.com> (raw)
In-Reply-To: <CALbNGRSGHYF0-9AgF7KmK8W_BBBOriVmx7FYupxySHUgdqKeYg@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-02-24 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 21:44 parse does not cache Andreas Müller
2013-02-24 0:48 ` Jason Wessel [this message]
2013-02-24 10:20 ` Andreas Müller
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=5129636A.1070706@windriver.com \
--to=jason.wessel@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=schnitzeltony@googlemail.com \
/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.