From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Image dependency broken
Date: Wed, 15 May 2013 09:42:52 -0600 [thread overview]
Message-ID: <5193ACFC.5070509@mlbassoc.com> (raw)
In-Reply-To: <1368629601.18324.1.camel@ted>
On 2013-05-15 08:53, Richard Purdie wrote:
> On Wed, 2013-05-15 at 15:46 +0100, Phil Blundell wrote:
>> On Wed, 2013-05-15 at 08:40 -0600, Gary Thomas wrote:
>>> * Build an image, e.g. core-image-sato
>>> $ bitbake core-image-sato
>>> * Cause some dependency to be rebuilt
>>> $ bitbake xserver-xorg -c cleansstate
>>> * Rebuild the image
>>> $ bitbake core-image-sato
>>
>> That's probably to be expected. You haven't done anything to actually
>> change the xserver-xorg package, just regenerated the same bits as you
>> had before, so there's no reason why the image would need rebuilding.
>>
>> Does it rebuild the image correctly if you do make a change to the
>> xserver-xorg package?
>
> Agreed, this is expected since the xserver-xorg output is unchanged and
> therefore the system is deciding it doesn't need to rebuild the image.
> If you change xserver-xorg somehow the checksum will change and the
> image will rebuild.
Understood. I'm sure that I had a recipe which did have such a change
that failed to cause my image to be rebuilt (not this contrived example
that I thought was the same). However, I can't make it happen now.
If it happens again, I'll get back to you.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-05-15 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:40 Image dependency broken Gary Thomas
2013-05-15 14:46 ` Phil Blundell
2013-05-15 14:53 ` Richard Purdie
2013-05-15 15:42 ` Gary Thomas [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=5193ACFC.5070509@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.