Hi, I am not an expert yet, but here is what I've recently done and I think this will give you some hints to what you want to achieve.
I've made a new meta layer so that I can use custom kernel and add new programs on top of existing core-image-* targets. I used qemu targets for now, but I also plan to extend this to other bsp so that I can use on different targets. Here is my meta-dl layer - https://github.com/insop/meta-dl Here is the lab that I've referred, see recipes-kernel and recipes-tools dirs - https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf Regards, Insop ========= Hi. I wish to write a custom meta layer that should add on-top of an existing bsp for eg. kernel and u-boot builds. But I want the custom layer to use .bbappend for some standard packages and also add some custom packages. My guess is that it might cause problems for the standard packages (since they are not unique) due to the MACHINE will be pointed out as the base bsp machine config, and the custom bsp will not define a machine on its own. Does this mean that I will have to define this new custom layer as a distro? I am worried that .bbappend stuff will never be executed since nothing will actually point to my custom layer for package recipes unless they are unique. What is the correct way to handle this use-case? Hans _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
