[yocto] clarification on what packages are *truly* needed for a yocto build?

Robert P. J. Day rpjday at crashcourse.ca
Wed Oct 9 03:45:36 PDT 2013


  (aside: prepping to teach an OE/yocto course in a couple weeks,
going thru the docs again, so be prepared for questions, some of them
potentially silly but all in aid of clarifying bits of documentation.
i'm sure scott rifenbark is currently steeling himself for the
experience. :-)

  i'm intimately aware of the current doc pages that list how to
establish your yocto build environment, such as this:

https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies

but a question or two.

  in some cases, i've seen, say, subversion listed as a prerequisite,
even though subversion is clearly built natively. so is it *truly* a
user-installable prerequisite? or am i misreading something?

  also, at this point, is there a list of what one can safely add to
ASSUME_PROVIDED to cut down build time on a new project? i recall from
way back when that, if you use ASSUME_PROVIDED, you're sort of voiding
the warranty in terms of what's been quality checked. but if one is
willing to take a chance, is there a set of packages that would be
considered "safe" to assume are provided? (for example, i would assume
that, in any current distro, git would certainly be safe, no?)

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



More information about the yocto mailing list