Okay, I'm going to start over :-) I have a layer, meta-poky, which is: $ git remote -v contrib git://git.pokylinux.org/poky-contrib (fetch) contrib git://git.pokylinux.org/poky-contrib (push) origin git://git.yoctoproject.org/poky (fetch) origin git://git.yoctoproject.org/poky (push)
Currently I have the master branch checked out from origin: f7afeeb75993b159bb8959e0309bc5eb3978a8fb I also have openembedded-core, which is: $ git remote -v contrib git://git.openembedded.org/openembedded-core-contrib (fetch) contrib git://git.openembedded.org/openembedded-core-contrib (push) origin git://git.openembedded.org/openembedded-core (fetch) origin git://git.openembedded.org/openembedded-core (push) Currently I have Khem's branch checked out: b0592ab08273e17cb1511384ad189281f88c8b03 For my layers I'm only using: meta-poky/meta-yocto (which I need so I can build an image with poky) openembedded-core/meta (which I need for Khem's work, including the qemumips64 MACHINE) My understanding is that the things in openembedded-core/meta are meant to replace the corresponding directories from meta-poky/meta, which is why I'm not including meta-poky as a layer. I am very confused by Robert's ability to build successfully with only the following two layers: BBLAYERS ?= " \ /home/rpjday/oe/dist/layers/oe-core/meta \ /home/rpjday/oe/dist/layers/openembedded-core-contrib/meta \ " Since, as far as I can tell, neither of them includes what is required to build a poky image. But I'll be trying out what Robert has done to see if I can get what he's getting :-) Maybe I'm still confused over all this meta-openembedded/openembedded-core stuff.
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
