All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] conf/bitbake.conf: allow cache reuse between bitbake, bitbake-layers and hob
Date: Wed, 22 Aug 2012 14:05:14 +0100	[thread overview]
Message-ID: <1345640714.3907.117.camel@ted> (raw)
In-Reply-To: <1345568909-10802-1-git-send-email-paul.eggleton@linux.intel.com>

On Tue, 2012-08-21 at 18:08 +0100, Paul Eggleton wrote:
> BB_ENV_EXTRAWHITE is set by the bitbake wrapper script but not by
> bitbake-layers, and thus it was affecting the data hash and thus
> invalidating the cache. Any variables passed through from the
> environment by being added to this variable should themselves
> influence the hash already if they are not already excluded from,
> the data hash, so BB_ENV_EXTRAWHITE can be excluded.
> 
> Similarly, DISABLE_SANITY_CHECKS is set by the hob script in order to
> have sanity checks run later, but not set by the bitbake wrapper script.
> It doesn't actually affect the build itself and so its value can also
> be excluded from the data hash.
> 
> These changes prevent unnecessary reparsing between executions of
> bitbake, bitbake-layers, and the initial pseudo build within the hob
> script.
> 
> Fixes [YOCTO #2680].
> 
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
>  meta/conf/bitbake.conf |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2012-08-22 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 17:08 [PATCH] conf/bitbake.conf: allow cache reuse between bitbake, bitbake-layers and hob Paul Eggleton
2012-08-22 13:05 ` 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=1345640714.3907.117.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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.