Thanks Khem for this extra insight.
toggle quoted messageShow quoted text
From: firstname.lastname@example.org [mailto:yocto-
email@example.com] On Behalf Of Khem Raj
Sent: Friday, June 28, 2013 12:59 PM
To: Burton, Ross
Subject: Re: [yocto] Documenting YP Development Environment in more
detail - user configuration
On Jun 24, 2013, at 7:57 AM, "Burton, Ross" <firstname.lastname@example.org>
meta-yocto is what makes Poky Poky, otherwise it would be just oe-coreyeah, meta-yocto could have been better name meta-poky that would have
+ bitbake. oe-init-build-env looks for sample files in $TEMPLATECONF,
which is one of the things that get munged as
bitbake+oe-core+meta-yocto becomes poky.
aligned the name
a bit. Its a distro layer much like other distro layers out there on
layerindex and then there is meta-yocto-bsp
layers which is much like any other machine layers out there.
a difference to point out is that poky uses the tooling to fudge all
layers together and create a single view
and is a leading user of combo-layer tooling provided by OE-Core. Other
distros keep the layers intact
slugos e.g. uses git submodules to maintain its layer setup. angstrom
has home-brew toolings and so on an so
forth. Both approaches have its own merits.
yocto mailing list