Hi I was writing a bitbake recipe for a project hosted on a git-server. I applied subpath in order to limit the checkout to a specific directory. When I ran the recipe it failed in do_fetch (or

On 16-04-15 13:00, testlaster wrote: Short answer: Put "inherit module" in your recipe to build the module. Example

Hi everyone. I would just like to know if it is possible to get the Yocto Kernel Header files? I need it to build a PCI driver but I cant seem to find a recipe or a download for it. Thanks and kind

Hello, For the last week or so I have been struggling to build a kernel image with an embedded initramfs using the mechanisms provided by Poky Daisy. In local.conf I have set INITRAMFS_IMAGE_BUNDLE

Hi David, There is no mechanism for this. There are two alternative means to do this kind of thing (just for the files that are already packaged by other recipes): A) Use bbappends on the original

Hi, I am building an image in daisy branch with both python and python3 included. It works to build the image itself but when trying to make an sdk with 'bitbake <image> -c populate_sdk' it fails

Hi Bruce, Hi Nikolay Thanks I'm never sure where to ask what :) I completely agree that it is not worth to breaking existing recipes because of that. But I think the option with an empty

After examining download logs it appears we could safely delete versions 1.0-1.3.x from http://adtrepo.yoctoproject.org/. They are only accessed by web crawlers at this point. Removing them would make

I am getting following error when i try to include driver as recipe in raspberrypi kernel NOTE: Executing write_package_manifest ... | DEBUG: Executing python function write_package_manifest | DEBUG:

Hello, I made a package recipe to merge files into my final rootfs (mostly init scripts under /etc). These files may be overriden by other packages so it is crucial that they remain intact. I am

All, Yocto Project 1.8 will be releasing this week! YP provides a major release every six months, and as an open source project we are always working to improve our processes. This survey is

And we could argue that having more inherits in the base is a bad thing for users that have no interest in device trees. One person's advantage is another's churn. I was looking for

Hi Bruce, Well, removing redundancy and simplifying users' recipes could be considered an advantage. Also, as the contents of linux-dtb.inc are going to be moved to bbclass, the file can be left

That is obvious. My questions are around "why". There's no big technical advantage, and if you remove that existing file, you break existing recipes. Which means you need to leave a stub in place. So

Hi Bruce, As far as I understood, Pascal's idea is to remove the need for user recipes to include linux-dtb.inc, and provide this functionality via inheritance. Regards, Nikolay

Hello all, I'm trying to get a simple build for the beagleboard with Yocto, but I'm getting some errors during the bitbaking. I'm running a virtual Ubuntu 14.04 on a 64-bit host. The build seems to

Adding oe-core, since that's the right place to have a discussion like this. True, but it has been like this for quite some time now :) The big trick with changing anything like this is

The sync is complete and broken symlinks are restored. I've also taken the opportunity to clean up absolute symlinks at the source so this issue cannot happen again even if the chroots aren't set

Hi As ARM now also moved to device tree it look like in future we will have more kernels that are using device tree then ones that are not. As far as I understand currently the generation of device

A change in the rsync configuration caused all symlinks to break during the most recent sync to the mirror front ends. The error has been corrected and the adtrepo links will be restored from the