linux-yocto-tiny drops the linux-tools and sets the KMACHINE branch to standard/tiny. Signed-off-by: Darren Hart <dvhart@...> --- meta/recipes-kernel/linux/linux-yocto-tiny/ata.cfg |

eglibc-utils RDEPENDS on bash which requires gettext which requires wchar support. If wchar support is not included in DISTRO_FEATURES, gettext will fail to compile. By removing eglibc-utils from the

Set ENABLE_WIDEC with ?= instead of = to allow for the external override by distro definitions. Signed-off-by: Darren Hart <dvhart@...> --- meta/recipes-core/ncurses/ncurses.inc | 2

From: Richard Purdie <richard.purdie@...> When looking for RDEPENDS to process, bitbake iterates through PACKAGES *and* PN. Since native.bbclass sets PACKAGES to be empty, its

RFC V2: o Use VIRTUAL-RUNTIME_keymaps as suggested by Martin Jansa o Drop poky-common abstraction as suggested by Richard Purdie in favor of POKY_DEFAULT_EXTRA_R* variables. Poky-tiny

tiny won't become compatible with the default kernel. linux-yocto-tiny will continue to exist in order to specify the KMACHINE and KBRANCH and possibly some other things. Much in the same way the

When: Thursday, December 22, 2011 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: Bridge Info Enclosed Note: The GMT offset above does not reflect daylight saving time adjustments.

Hrm, it reported parsing errors on the ${@oe_filter_out not being defined as well as the "require utils" I added to address that. Maybe I'm missing something else. But, I think I'll be taking the

Actually, -ENOPEPSIYET, meta-yocto doesn't come into this as I defined linux-yocto-tiny_3.0.bb in oe-core. meta-tiny doesn't come into this either though. The poky-tiny patch series doesn't introduce

I suggesting meta-dri2/meta-intel depending on meta-tiny is a problem. Where does meta-yocto come into this? Cheers, Richard

If that works, sure, but that wasn't my intent. You can include/require a .inc from a .conf. That seems reasonable. Event handlers are used in a number of places in the metadata, including

Right, I'd expect you are totally overriding DISTRO_FEATURES anyway. Right now you need to override these things, in future I suspect you're going to want to share them when tiny becomes compatible

Hrm, good point. My goal was to eliminate meta-tiny altogether. I have never built meta-intel without meta-yocto. Do we feel that dependency a problem? -- Darren Hart Intel Open Source Technology

Aha, now I remember. Consider things like the following, defined in poky.conf: DISTRO_FEATURES_append = " largefile opengl" This one, not so bad, I can easily override

I'd just note that if merged, this would make meta-fri2 depend on meta-tiny since we'd throw parsing errors if the .bbappend is present without the file its appending to. We might want to consider

This is likely due to a buggy BIOS. See the README.hardware section about formatting the disk as USBZIP format. We hope to address this with a more robust live hddimg type in the future. -- Darren

I seem to recall something about this being harder with tiny as it removes things rather than just extending. But I can't put recall exactly what the issue was (or if there was one). I shall try it

Why doesn't something like: """ $meta-yocto/conf/distro$ cat poky-lsb.conf require conf/distro/poky.conf DISTRO = "poky-lsb" DISTROOVERRIDES = "poky:linuxstdbase" """ work? Effectively the above

While running a build of the core-image-sato using the edison latest commits and the meta-cedartrail bsp, I notices some errors fly by and thought I'd see if anyone knows the reason. The build

See this thread http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001498.html Cheers, -- Martin 'JaMa' Jansa jabber: Martin.Jansa@...