On 2/20/11 9:50 AM, Chris Tapp wrote: > On 20 Feb 2011, at 15:37, Mark Hatle wrote: > >> To me it looks like it deleted exactly what you asked it to. All of >> the >> sstate-netbase-* files, and the downloaded netbase_4.41.tar.gz. > > It's not that easy to see when the lines get mangled. Below are the > ends of the 'ls' and 'cleanall' names for _populate_sysroot. > > sstate: -7422fec9d26be091358f8e930110bf37_populate-sysroot.tgz > (existing file after build) > NOTE: -4c81cdca2e1c8da43ee609321b93895f_populate-sysroot.tgz > (cleanall delete target) > > Doesn't this show that the wrong one was targeted for deletion?
No, the md5sum is the signature of the recipe. If the signature changes, it should avoid the sstate-cache and rebuild. If it's still pulling in the version from the sstate, even though the signature changed.. this could indicate a problem. (Any time you change the recipe or referenced files in the recipe the signature should be changing... this won't trigger a rebuild though until you do a bitbake -c clean ... It will recompute the signature, see it doesn't match the sstate and build...) --Mark >> For the latest changes in master, we've got planned a bit more >> control then >> simply "clean" and "cleanall", but I don't believe it's implemented >> yet. > > That sounds interesting. For example, it would be nice to be able to > clean everything except the download (useful when working off-line). > > Chris > > _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
