i'm still a bit unclear on the differences(?) between what is listed
as "required packages for the host development system" in the
reference manual, and what's listed as ASSUME_PROVIDED in the oe-core
bitbake.conf file.
should those two lists not match? for instance, the ref manual
states that, for example, "unzip" is an essential native package. but
that's not mentioned in bitbake.conf as ASSUME_PROVIDED. am i
misunderstanding the purpose of ASSUME_PROVIDED?
if you scan across the supported distros, there are a number of
software packages that are listed as "essential" in one or more places
(diffutils, for example) that aren't mentioned in bitbake.conf.
so what's the relationship here?
rday
p.s. i'm aware that one can use ASSUME_PROVIDED to bypass the step of
building a native package if one is supremely confident that that
package is compatible with yocto. i've used that to skip building
subversion for a number of recent builds, as one example.
would there be any value in a script that pokes around the dev host
and reports back what *appear* to be adequately recent dev packages?
i'm aware that that would void my warranty :-), but given a suitably
recent distro, i'm assuming that quite a number of required dev tools
would match what's already installed and save quite a bit of time
building from scratch.
does such a script exist?
--
========================================================================
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
