In a sense yes. From how I understand it, anything that is listed as a required utility in SANITY_REQUIRED_UTILITIES does not even have to be listed in ASSUME_PROVIDED. The required native utilites should fail the sanity test right away if they are not there.
For any dependency listed in ASSUME_PROVIDED BitBake will not attempt to build it. But for instance, even if you do not list "tar-native" in ASSUME_PROVIDED there is no way for BitBake to build tar since the recipe's SRC_URI points to a tarball. Catch22. However, I would expect that all the build essentials (awk make wget tar bzip2 gzip python unzip perl patch diffutils diffstat git cpp gcc gcc-c++ eglibc-devel texinfo chrpath ccache) are listed in SANITY_REQUIRED_UTILITIES. A reason I could see to list all of the required native utilities in ASSUME_PROVIDED could be the dependency graphs. It does not really add any value to show the native stuff in the graphs. :rjs
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
