[oe] How does oe handle rebuilds?

Hauser, Wolfgang (external) Wolfgang.Hauser.external at cassidian.com
Tue Mar 8 09:38:31 UTC 2011


As I see it is recommended by the community to do a build "from scratch" if main features as e.g. kernel version has changed.

Removing the temporary directory and do an overnight build is the easiest and cleanest resolution.

Regards
Wolfgang
 
-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces at lists.openembedded.org [mailto:openembedded-devel-bounces at lists.openembedded.org] Im Auftrag von Charles Manning
Gesendet: Montag, 7. März 2011 18:58
An: Openembedded-devel at lists.openembedded.org
Betreff: [oe] How does oe handle rebuilds?

I find I often have problems when using oe that changing a recipe does
not result in dependent packages being rebuilt. A bit of Googling
suggests that many experience this issue and take manual steps to
force rebuilding.

For example, changing the kernel requires rebuilding various libraries
(tslib etc) and rebuilding the image.

1.Should oe be able to handle that automatically or is this oe's
"killer defect" (ie. opposite of "killer feature").
2. Is there something missing in recipes to show the correct dependencies?
3. What is the best way to manage these stale dependencies?

Thanks

Charles

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel at lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




More information about the Openembedded-devel mailing list