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
------------------------------------------------------------
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
