On 12/11/14 12:14, Paul Eggleton wrote: >> It's not supposed to behave this way, although I have reproduced it here - I >> think I hadn't actually tested rebuilding an image with a recipe in the >> workspace added to the image. The problem is that the do_compile task is >> being marked as nostamp, but the way bitbake behaves now, that doesn't >> cause any dependent task signatures to be changed and thus no dependent >> tasks get run afterwards. Either I'll have to change that or work out a >> different way of ensuring do_compile and dependent tasks get run - either >> way, you should only have to run a build that calls for the recipe (be it >> the recipe itself or something that depends upon it), no cleaning/resetting >> should be needed. I'll try to fix this tomorrow. > OK, I've fixed this on the branch as well. You should now find that > rebuilding > the image always triggers a compile -> install -> package etc. of the > recipe(s) in the workspace first. (It'll end up triggering other recipes to > rebuild as well if they are in the chain; we may have to address that > differently later for cases where that's annoying).
Ok great. I've re-tested and it all seems good. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
