-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
For the past few months I have been maintain a so called "layer" to build angstrom on top of the yocto stuff. So after a few months working with yocto I can give a better assesment: Yocto people worked on making yocto better buildsystem, while OE people worked on making the output of OE better. So currently, for anything besides sato yocto is a toy. The good news is that with the meta-openembedded layer (http://cgit.openembedded.org/cgit.cgi/meta-openembedded/log/) we can build something as simple as console-image :) As you can see from the log, work on adding extra recipes like qt4 is being worked on. Apart from the lack of metadata there are a number of bugs in yocto that make it unsuitable for general consumption: * (PRE)MIRRORS are broken in yocto, so fetching sources becomes a hassle. Combined with the broken git fetcher you need regular OE to fetch things first into a shared DL_DIR. * Multimachine builds are broken. You can only have one set of task-base packages at a given time. So you can't do this: MACHINE=beagleboard bitbake task-base MACHINE=omap3evm bitbake task-base All this has been reported to the yocto people, let's see if they fix it. If people want to test/help/etc, check out the 'yoctoproject' branch of the setup scripts: http://gitorious.org/angstrom/angstrom-setup-scripts/commits/yoctoproject That is currently the easiest way to get a working bblayer setup. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNIbbrMkyGM64RGpERAmkhAJ9bOxEUSraU5Nz+9IpkBTPe+S2NAgCeKpDx I+7K91BYLdl54SbZ/uAukLs= =JkTv -----END PGP SIGNATURE----- _______________________________________________ Angstrom-distro-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
