Chatted with TomZ on #yocto on freenode IRC, it looks like I did not perform the steps in section II from README in meta-intel/meta-crownbay. It is likely that that's what I am missing.

I am bitbaking core image sato for machine corwnbay (with the emgd driver) and the emgd-driver-bin recipe seems to fail. Here is the error. I searched the archives, but could not find

The paths issue your are speculating on was fixed by myself and Richard last November. I would suggest running bitbake-diffsig to determine the actual sstate differences. -M On Feb 3, 2012 10:51 PM,

I've added the reset option (restores the directories' default values) to the Settings design document. The new version is

Hi Joshua, Additional package details appear on clicking the package name using an information bubble. The bubble is also dismissed on click using a 'close' button. This functionality is shown on the

If there is standardised SECTION variable why not use recipes-${SECTION}/foo_1.0.bb as we already have couple of recipe-* directories and it's sometimes hard to decide to which directory something

I have replaced 'udev' by 'udev-extraconf udev-cache udev-utils libudev libgudev', but no luck. the udev is still included which result glib-2 included. -- Yi

does the dependency you said can be found in the bb file? I only found glib-2.0 in the udev's dependency in udev.inc. and in hob, it said that: the glib-2.0 is brought in by udev-utils, udev-acl,

thanks! -- Yi Qingliang niqingliang@... https://niqingliang2003.wordpress.com

its udev-acl and udev-consolekit which needs it. You can avoid that in your image dependencies

hello, All: I'm trying to build my own image-lsb-core, and making LFS as reference. In LFS, there is not glib-2.0, in other words, udev can be used without glib-2.0. What can I do if I want use

A quick look at the patches themselves shows them to not be valid kernel patches. The files don't have the right sub-path, so there's no way you'll ever patch the kernel with these changes. My

Thanks! I'll run some tests here and see what I can find. Cheers, Bruce

Glad to know my recollection isn't wildly off the mark. I noticed that there are similar, yet different, SECTION values being used. If we opt to keep SECTION I wonder if we should try and

Okay, I've made some edits using the == Heading Level 2 ==. I think it solves some of my issues for editing, etc. Only need the complete edit for starting a new topic, I guess.

Hi Tal, First, thanks for checking and considering using Yocto Project. Please send your future questions toyoct@... mailing list, that’s the general mailing list for all Yocto project related

\>>>>>>>>> I could not find a way to patch the kernel source before its is I will try that next. However, it seems like something is wrong with my setup may be. I was reading the log.do_patch file

Every build that I do with my meta-kernel-dev has some out of tree patches. It's a form of continual regression testing that I do out of habit. My bbappend looks like this: SRC_URI =

Indeed, that's precisely what I'm recommending. Further, when we need to colour a widget that isn't usually coloured in the theme (like the red/green colouring of build items in the hobv1) we should

Agenda   * Opens collection - 5 min (Song) * Yocto 1.1.1 point release update - 10 min (Josh/Beth) * Yocto 1.2 M3 status - 10 min (Song/Team)