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

Sure, it'll take me a bit to get access to the infrastructure but I'll get to it when I have access. -b -- Elizabeth Flanagan Yocto Project Build and Release

Hi Todor, Created an bug 7612. Also w.r.t to hello world example I was using the Standalone pre-built tool chain option. Also this work only for the Hello World template project and if select empty

Hello Abhinav, In your previous email you mentioned that the cross compiler variables are populated for the hello world example. If that's the case the IDE must have parsed the environment setup

Hi Todor, I tried with below link and still observe the same issue. It didn’t identify the bitbake directory environment files and report same errors. Thanks, Abhinav

Hi, I was trying to setup Eclipse (Kepler) for Yocto Plugin and facing issue when I try to create project other than hello world. If I select Yocto CMake Empty project I don’t see the tool

Hi All, I downloaded the yocto from the following link: git clone -b dizzy git://git.yoctoproject.org/poky.git And added the my custom recipe for downloading our custom kernel from SVN. My recipe