On Friday 16 May 2014 08:51:35 Robert P. J. Day wrote: > On Fri, 16 May 2014, Paul Eggleton wrote: > > So apologies for not replying earlier - I've not been directly > > involved in the BSP for Galileo, but I have been providing support > > for the team doing the IoT DevKit work. You should be able to build > > images for Galileo using what's in meta-intel-iot-devkit directly; > > you could also use the layers within it separately using your own > > separate OE-Core / Poky tree, but it's not really designed to be > > used in that way. If you really want to do it separately you should > > take care to use all three layers (meta-clanton-bsp, meta-galileo, > > and meta-iot-devkit) and set your DISTRO = "iot-devkit". > > possibly a silly question, but what are the dependencies between > those three layers? i'm used to seeing layer dependencies listed in a > layer's "layer.conf" file. if i look at the meta-iot-devkit layer, its > layer.conf file says nothing about dependencies, but one of its kernel > recipes, "linux-yocto-clanton_3.8.bbappend", is clearly a reference to > a kernel recipe in the meta-clanton-bsp layer. > > i would thus have expected to see that dependency listed in the > layer.conf file. has something about listing layer dependencies > changed while i wasn't looking?
No, nothing has changed. The separation here is probably not as clearly defined as it ought to be. I guess what I'd say is, you shouldn't look at this as a fully worked example of how to structure things; it was put together out of various pieces and intended to be used as a whole rather than separate components. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
