Yoctoproject

-----> make sure INHERIT += "rm_work" is commented out kernel fiddling will not work with it press to go on <----- example 1 example 2 example 3 example 4 What works for me: restore original kernel: bitbake virtual/kernel -c clean -f bitbake virtual/kernel -c configure -f #bitbake virtual/kernel -c menuconfig bitbake virtual/kernel -c compile -f bitbake virtual/kernel -c deploy -f bitbake virtual/kernel configure default kernel: bitbake virtual/kernel -c configure -f bitbake virtual/kernel -c menuconfig -f bitbake virtual/kernel -c deploy -f bitbake virtual/kernel

bitbake virtual/kernel -c menuconfig

If you get: ERROR: Function 'File: '/work/rber/poky-bernard-5.0.1-arm-beagle/downloads/distcc-2.18.3.tar.bz2' has md5 checksum 2279f50fe7b688c8d6762a3e095a302a when 0d6b80a1efc3a3d816c4f4175f63eaa2 was expected (from URL: 'http://distcc.samba.org/ftp/distcc/distcc-2.18.3.tar.bz2')' failed better: 1) bitbake distcc -c cleanall 2) bitbake distcc -c fetch as this will force a clean out of any existing "bad" state that might exist. The -f option means rerun the task even if bitbake doesn't think it needs to run but it will not wipe out files in DL_DIR. or (not so good) ... 1) refetch distcc $ bitbake -c fetch -f distcc If that still fails: 2) update the MD5 in the distcc recipe and try to rebuild. If that works, we need a patch to update the MD5. or ... check if the file you want to fetch still exists at the URL you try to fetch it from;)

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