Yoctoproject

from here These are build objects if you don't need them add INHERIT += "rm_work" to your conf/local.conf which should delete the intermediate objects after a recipe builds.

build: poky-image-sato-sdk bitbake meta-ide-support I want to have my rootfs nfs exported so I can customize it. extract rootfs: mkdir -p ${POKY_BUILD_NAME}-rootfs poky-extract-sdk tmp/deploy/images/poky-image-sato-sdk-qemux86.tar.bz2 ${POKY_BUILD_NAME}-rootfs You might want to install an nfs server and a tftp server as well so you have everything you need for running the stuff on a real target instead of qemu. run: poky-qemu qemux86 ${POKY_BUILD_NAME}-rootfs

On the first look the release tag and the release tarball don't seem to be the same as you can see here . ... that comes from the fact that the release git tag was moved. git pull is not enough;) you also need to: git fetch --tags From git://git.pokylinux.org/poky - [tag update] bernard-5.0 -> bernard-5.0

We'll see first how to compile the thing. here you can see: qt4 is part of the yocto meta data. The poky-image-sato-sdk image contains the qt4-pkgs, so you can use the following command to build the image: bitbake poky-image-sato-sdk

This tip can be found here . Here we add as an example an openembedded package to yocto/poky, or to be precise from oe.dev to meta-oe A working recipe can be found here . In order to rebuild the package clean and build are not enough. This is what you need to do: % bitbake tcpdump -c clean % rm -f sstate-cache/sstate-tcpdump* % bitbake tcpdump