i know i've mentioned this before, but it's still somewhat confusing if a new yocto user wants to figure out *exactly* what he or she must install manually on a yocto development host.
there are a pile of web pages that claim to explain this: http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html http://www.openembedded.org/index.php?title=OEandYourDistro http://www.openembedded.org/index.php?title=Required_software http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#required-packages-for-the-host-development-system but they're inconsistent, and the bigger issue is this in bitbake.conf: ASSUME_PROVIDED = "\ bzip2-native \ chrpath-native \ git-native \ grep-native \ diffstat-native \ patch-native \ perl-native-runtime \ python-native-runtime \ tar-native \ virtual/libintl-native \ " # gzip-native should be listed above? it would *seem* that, for efficiency, the build process should take far more advantage of already-installed native packages. the above list is kind of weird in its selective inconsistency -- why is git there but not subversion? why is bzip2 but (as you can read) not gzip? in addition, some of the above links insist that you need to install (for instance) m4, but it's obvious that m4 is going to be downloaded and built for you. the same with quilt, i believe. anyway, you get the idea. i think it was tom z(?) who explained once that downloading and building even some natively-installed tools made Q/A easier, and that's certainly true. but it would also be useful, for efficiency, to at least *suggest* to readers what native tools they might take advantage of, with a minimum supported version of each. thoughts? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto