Attendees: Jeff, Beth, Paul, Darren, Tom, Jessica, Joshua, Matthew, Sean, Saul, Richard, Dave, ScottR, Song   Agenda:   New Action Item List: 1. Richard will review unsorted features and prioritize

Attendees: Jeff, Beth, Paul, Darren, Tom, Jessica, Joshua, Matthew, Sean, Saul, Richard, Dave, ScottR, Song   Agenda:   New Action Item List: 1. Richard will review unsorted features and prioritize

This link has been fixed and the 1.1 version of the manual on the web reflects the change (http://www.yoctoproject.org/docs/1.1/adt-manual/adt-manual.html). I will request a backport into Edison for

Hi Michael, Thanks for reporting the issue and we’ll have it fixed. Thanks, Jessica

I've implemented two new ways of keeping up with the yocto autobuilder's build status (other than the obvious way of looking at autobuilder.yoctoproject.org:8010 of course) First is through the

pull into my local repos, I'll have an update for this later today or early tomorrow. Bruce

Thanks Kishore! Acked-by: Darren Hart <dvhart@...> -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

From: Kishore Bodke <kishore.k.bodke@...> Add rt support to the meta branch for romley. Signed-off-by: Kishore Bodke <kishore.k.bodke@...> ---

From: Kishore Bodke <kishore.k.bodke@...> Hi All, This is the patch to support rt in the kernel meta branch for romley. Please pull into linux-yocto-3.0/meta and

Hi Anders, I looked into this yesterday and there's definitely a problem. I have filed bug #1760 [1] to track it and as described there should have a working fix very soon. Thanks for the concise

Hi, The wiki pages for "build appliance" and "hob v2" are updated at https://wiki.yoctoproject.org/wiki/Build_Appliance_Design https://wiki.yoctoproject.org/wiki/Hob2_(Hob_v2) Feel free to

when using the yocto ADT in eclipse, I want to specify the toolchain location by path variables, but only got error! It looks like other preference can support the path variable. any ideas? I want

So if I wanted to build Firefox into my Yocto project. How is that done?? Jim A

It's actually a combination of both worlds - you can use existing recipes to add functionality by just including those packages in your system, either at initial build time or by using the packaging

Hi James, The approach you describe is followed by a number of embedded developers. There are advantages to starting with a known-working quantity and scaling it down, particularly one with a working

I thought the idea was to build a recipe for your device that could create the software complete with all the pieces. Certainly, having a list of packages that you need to install via zypper is fine,

Using very similar tools - zypper is just like yum, or if you choose to use ipk packages, opkg -- ------------------------------------------------------------ Gary Thomas |

I approach embedded Linux from a path of taking a Distro like Ubuntu or Fedora and chopping it down to a working set of code that forms the final solution. Obviously, not the same methology as Yocto.

All, Here is my tentative plan for the upcoming cut off times for 1.2 milestone releases. Working backwards from when the buildout needs to be delivered to QA: Milestone Build Finished and Delivered

Agenda:   * Opens collection - 5 min (Song) * Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh) * Yocto 1.2 planning and M1 Status - 10 min