On 12/23/2011 08:43 AM, Paul Eggleton wrote: > On Friday 23 December 2011 14:23:53 Koen Kooi wrote: >>> Being a Yocto newbie, it's hard enough to understand all the branches on >>> the yocto site. Relating the meta-angstrom is confusing. >> >> No, yocto (or is it poky? noone knows) > > Officially, Poky is the build system, Yocto is the umbrella project which > also > includes a number of other sub-projects (swabber, pseudo, etc.). There are > some that use Yocto to refer to the build system; I'm not sure that does a > great deal of harm nor is it really relevant to this discussion. > >> has confusing messaging, It's best to >> find the official BSP for the board you use and follow the instructions in >> there and ignore anything else. > > Personally I think this is a bit disappointing. The Yocto Project and the > move > to OE-Core is supposed to provide us a way to mix and match hardware support > with available software packages. The apparent tying of meta-texasinstruments > to meta-angstrom goes against that philosophy, IMHO. I haven't yet heard a > compelling technical argument for why that should be necessary.
BSP's shoudl contain image recipes that create useful images for the hardware. Images often tend to contain distro specific bits and pieces. This leads to this sort of (problematic) dependencies between layers. This is good area for further study since the problem will likely increase without careful thought. I'd also suggest not depending on the BSP guys to do this, since I suspect their corporate overlords care more about the output and customer satisfaction then internal "details". Philip _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
