On Fri, 19 Apr 2013, Tom Zanussi wrote:
> On Fri, 2013-04-19 at 08:37 -0400, Robert P. J. Day wrote:
>
> > second, the BBLAYERS example there seems overly complicated and
> > potentially confusing to beginners. the fact that meta-yocto is listed
> > as NON_REMOVABLE might make readers wonder how they're supposed to
> > know that. why not go with something a lot more people will see, like,
> > say:
> >
> > BBLAYERS = ?" \ <-- and that looks like a typo
> > /usr/local/src/yocto/meta \
> > /usr/local/src/yocto/meta-ti \
> > "
> >
> > BBLAYERS_NON_REMOVABLE ?= " \
> > /usr/local/src/yocto/meta \
> > "
> >
>
> I agree - the whole NON_REMOVABLE thing doesn't add anything and should
> be removed - the example is just trying to show how to add a BSP layer -
> the rest just adds potential confusion. And, yeah, it's a typo..
i'll let someone else decide what to do there.
> > finally, the passing reference to layers that contain sub-BSP-layers
> > is good, but show an example, such as the fact that the meta-crownbay
> > layer.conf file has a dependency on meta-intel:
> >
> > ...
> > LAYERDEPENDS_crownbay = "intel"
> >
> > never pass up the opportunity to reinforce an idea with a few lines
> > of actual code. :-)
> >
>
> Agreed, but on the other hand we don't really want to be too
> intel-specific (I know, we have crownbay everywhere else, but anyway..)
i was just looking for an example of the kind of hierarchical layer
structure you find in meta-intel. is there another layer that has that
kind of structure?
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
