Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/1 V2] bitbake-whatchanged: print what is about to happen
Date: Sat, 11 Aug 2012 10:05:25 +0800	[thread overview]
Message-ID: <5025BDE5.8060805@windriver.com> (raw)
In-Reply-To: <9608773.T2XBm9ArBe@helios>



On 08/10/2012 10:28 PM, Paul Eggleton wrote:
> On Friday 10 August 2012 11:47:38 Robert Yang wrote:
>> Changes of V2:
>>
>> * Fix a typo fn -> 'fn'
>>
>> * Use "bitbake -e" rather than "bitbake -e recipe" to get the BB_STAMPS_DIR
>>
>> * Use "BB_STAMPS_DIR=<path> bitbake -S recipe" to regenerate the stamps
>>
>> * Change the summary format a little, now it looks like:
>>    - (without -v):
>>      === Summary: (3653 changed, 1927 unchanged)
>>      Newly added: 807
>>      PV changed: 48
>>      PR changed: 276
>>      Depends changed: 2522
>>
>>    - (with -v):
>>      === Summary: (3653 changed, 1927 unchanged)
>>      Newly added: 807
>>      Depends changed: 2846
>>
>> // Robert
>>
>> The following changes since commit 2dec760b79bb7e2e79c33c5127fa64685bd86a18:
>>
>>    foomatic: fix perl path for target (2012-08-08 10:06:00 +0100)
>
> So leaving Chris's objections aside for a moment, I applied this and the
> BB_STAMPS_DIR change, and ran the script on my build directory which is out of
> date with respect to the metadata (i.e. metadata has been updated since the
> last build). The output seems to suggest that no changes have been made, which
> is not the case:
>

Thanks Paul, did you re-run the oe-init-build-env, please? Otherwise the
BB_STAMPS_DIR would have no effect since it would not  be in the BB_ENV_EXTRAWHITE.

// Robert

> ----------- snip -----------
> $ bitbake-whatchanged core-image-minimal
> Figuring out the BB_STAMPS_DIR ...
> Generating the new stamps ... (need several minutes)
>
> === Summary: (0 changed, 0 unchanged)
> Newly added: 0
> PV changed: 0
> PR changed: 0
> Depends changed: 0
> ----------- snip -----------
>
> Cheers,
> Paul
>



  reply	other threads:[~2012-08-11  2:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  3:47 [PATCH 0/1 V2] bitbake-whatchanged: print what is about to happen Robert Yang
2012-08-10  3:47 ` [PATCH 1/1 " Robert Yang
2012-08-10 13:38   ` Chris Larson
2012-08-11  3:38     ` Robert Yang
2012-08-10 14:28 ` [PATCH 0/1 " Paul Eggleton
2012-08-11  2:05   ` Robert Yang [this message]
2012-08-11  3:10     ` Robert Yang

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=5025BDE5.8060805@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=bitbake-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox