Re: [yocto] PREFERRED_PROVIDER in image recipes

2013-01-29 Thread Bruce Ashfield
On 13-01-28 11:16 AM, Daniel Kenji Morgan wrote: Sorry to bring up an old post, but I haven't managed to find information in the mail archives and bugzilla on how the issue stands as of today. The post I am referring to is as follows: https://lists.yoctoproject.org/pipermail/yocto/2011-December

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, January 29, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

2013-01-29 Thread Liu, Song
Attendees: Illeana, Nitin, Amit, Richard, ScottR, Belen, BruceA, TomZ, LaurentiuP, Corneliu, Mark, Björn, Kevin, Saul, Ross, AlexG, JessicaZ, BogdanM, DarrenH, SongL.   Agenda:   * Opens collection - 5 min (Song) * Yocto Project 1.3.1 status - 10 min (Ross) - Ross: nothing new. We should be

Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY

2013-01-29 Thread Rifenbark, Scott M
Thanks. Sounds like it would be useful to document this variable. From: kerg...@gmail.com [mailto:kerg...@gmail.com] On Behalf Of Chris Larson Sent: Tuesday, January 29, 2013 1:10 PM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org Subject: Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY On Tue, Jan 2

Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY

2013-01-29 Thread Chris Larson
On Tue, Jan 29, 2013 at 1:58 PM, Rifenbark, Scott M < scott.m.rifenb...@intel.com> wrote: > I can't seem to find any information on this variable other than what was > offered in a bug (https://bugzilla.yoctoproject.org/show_bug.cgi?id=3662) > filed against some stuff in the glossary in general.

Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY

2013-01-29 Thread Rifenbark, Scott M
Good information... thanks! >-Original Message- >From: Trevor Woerner [mailto:twoer...@gmail.com] >Sent: Tuesday, January 29, 2013 1:06 PM >To: Rifenbark, Scott M >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY > >On Tue, Jan 29, 2013 at 3:58 PM, Rifenbark, Sc

Re: [yocto] BB_DANGLINGAPPENDS_WARNONLY

2013-01-29 Thread Trevor Woerner
On Tue, Jan 29, 2013 at 3:58 PM, Rifenbark, Scott M wrote: > Can anyone out there offer more information on this variable? Wondering > whether this should be documented in the glossary. By default bitbake will throw an error if there exists a *.bbappend recipe for which there is no correspondin

[yocto] BB_DANGLINGAPPENDS_WARNONLY

2013-01-29 Thread Rifenbark, Scott M
I can't seem to find any information on this variable other than what was offered in a bug (https://bugzilla.yoctoproject.org/show_bug.cgi?id=3662) filed against some stuff in the glossary in general. The information provided there by Robert P. J. Day says it is handy when layers get out of syn

Re: [yocto] [yocto-docs][PATCH 0/3] Archiver documentation updates

2013-01-29 Thread Rifenbark, Scott M
Kevin, Thanks for the fixes. I cherry-picked them from your contrib area and they are now in yocto-docs/master. Scott >-Original Message- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Kevin Strasser >Sent: Monday, January 28, 2013 3:06 P

Re: [yocto] SRC_URI scope and kernel fragments in non-yocto kernel recipes

2013-01-29 Thread Bruce Ashfield
On 13-01-29 06:24 AM, stephen.lawre...@renesas.com wrote: Bruce Ashfield wrote on 28/01/2013 18:56:02: Why is the SRC_URI containing the additional patches applied when referenced directly in the bb file, but not when referenced in an include or scc file? Keeping the question isolated to jus

[yocto] [PATCH] Add sbindir_nativesdk to environment setup

2013-01-29 Thread Wolfgang Denk
When adding for example file system generating tools like "mkfs.cramfs" or "mkfs.ubifs" to the SDK, these will be installed into the "${prefix_nativesdk}/sbin" directory, but the generated environment-setup script sets a PATH that includes /bin only. Add a new definition of "sbindir_nativesdk" and

Re: [yocto] SRC_URI scope and kernel fragments in non-yocto kernel recipes

2013-01-29 Thread stephen . lawrence
Bruce Ashfield wrote on 28/01/2013 18:56:02: > Why is the SRC_URI containing the additional patches applied when > referenced directly in the bb file, > but not when referenced in an include or scc file? > >>> > >>> Keeping the question isolated to just the patch on the SRC_URI is