51 AM
>To: Rifenbark, Scott M
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>
>
>On 7/8/13 10:54 PM, "Rifenbark, Scott M"
>wrote:
>
>>Here is a link to draft section o
octoproject.org [mailto:yocto-
>>boun...@yoctoproject.org] On Behalf Of Burton, Ross
>>Sent: Tuesday, June 25, 2013 2:55 AM
>>To: Philip Balister
>>Cc: yocto@yoctoproject.org
>>Subject: Re: [yocto] Documenting YP Development Environment in more
>>detail - user configurat
>boun...@yoctoproject.org] On Behalf Of Burton, Ross
>Sent: Tuesday, June 25, 2013 2:55 AM
>To: Philip Balister
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>On 25 June 2013 01:39, Philip Balister
It looks like the community freescale work at github is using it too:
https://github.com/Freescale/fsl-community-bsp-platform
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>
>On Jun 24, 2013, at 7:57 AM, "Burton, Ross"
>wrote:
>
>> meta-yocto is what makes Poky Poky, otherwise it would be just oe-core
>> + bitbake. oe-init-build-env looks for samp
On Fri, Jun 28, 2013 at 10:02 PM, Khem Raj wrote:
> We use android repo internally to manage the layers and I think there are
> projects out there like here
>
> http://www.jann.cc/2012/08/08/building_freescale_s_community_yocto_bsp_for_the_olinuxino.html
>
> which are also using android repo to ma
On Jun 24, 2013, at 10:15 PM, Rudolf Streif wrote:
> Hi Trevor,
>
>
> On Mon, Jun 24, 2013 at 5:56 AM, Trevor Woerner
> wrote:
> Awesome! That's great news! I was hoping someone would "beat me to it"
> :-) I look forward to reading it once it's done. Do you have a
> publisher or an expected
On Jun 24, 2013, at 7:57 AM, "Burton, Ross" wrote:
> meta-yocto is what makes Poky Poky, otherwise it would be just oe-core
> + bitbake. oe-init-build-env looks for sample files in $TEMPLATECONF,
> which is one of the things that get munged as
> bitbake+oe-core+meta-yocto becomes poky.
yeah, m
> not integrate with yocto directly. but use it to 'manage' the set of trees
> that are required when using OE/Yocto. The gumstix guys are using it, see
> [1], and we are moving toward it at linaro too, to manage our builds [2]
>
> [1] https://github.com/gumstix/Gumstix-YoctoProject-Repo
> [2] http
On 25 June 2013 01:39, Philip Balister wrote:
> I totally agree we drifted way beyond the initial discussion of the
> figure. The key thought here is understanding how Poky differs from a
> typical use of oe-core + other layers.
Is there such a thing as a "typical" use of oe-core + layers? Poky
On Tue, Jun 25, 2013 at 7:15 AM, Rudolf Streif
wrote:
>
>
>> An appendix on Android's "repo" tool might make for an excellent
>> addition; it seems some Yocto projects are showing lots of interest in
>> using it.
>>
>> The idea is to integrate/use it with YP? I know what repo does and that
> it is
Hi Trevor,
On Mon, Jun 24, 2013 at 5:56 AM, Trevor Woerner
wrote:
> Awesome! That's great news! I was hoping someone would "beat me to it"
> :-) I look forward to reading it once it's done. Do you have a
> publisher or an expected release date?
>
> Yes, I do. Pearson and the release date is earl
On 06/24/2013 02:37 PM, Jeff Osier-Mixon wrote:
> On Mon, Jun 24, 2013 at 11:25 AM, Philip Balister wrote:
>> Showing how Poky (the reference distribution) is built would be a nice
>> way to introduce people to building their own custom distributions using
>> OpenEmbedded.
>
> Totally agree, but
On Mon, Jun 24, 2013 at 11:25 AM, Philip Balister wrote:
> Showing how Poky (the reference distribution) is built would be a nice
> way to introduce people to building their own custom distributions using
> OpenEmbedded.
Totally agree, but I would relegate that to a separate effort. The
main prob
On 06/24/2013 12:59 PM, Burton, Ross wrote:
> On 24 June 2013 17:55, Philip Balister wrote:
>> Explaining how poky is built up from oe-core + meta-yocto +
>> meta-yocto-bsp + some other stuff would be really helpful in reducing
>> confusion over what all the pieces are and where they come from.
>
.
>-Original Message-
>From: Philip Balister [mailto:phi...@balister.org]
>Sent: Monday, June 24, 2013 9:56 AM
>To: Rifenbark, Scott M
>Cc: Burton, Ross; Robert P. J. Day; yocto@yoctoproject.org
>Subject: Re: [yocto] Documenting YP Development Environment in more
>detail
On 24 June 2013 17:55, Philip Balister wrote:
> Explaining how poky is built up from oe-core + meta-yocto +
> meta-yocto-bsp + some other stuff would be really helpful in reducing
> confusion over what all the pieces are and where they come from.
Agreed - explaining clearly that Poky is mostly an
all the pieces are and where they come from.
Philip
>
> Scott
>
>> -Original Message-
>> From: Burton, Ross [mailto:ross.bur...@intel.com]
>> Sent: Monday, June 24, 2013 7:57 AM
>> To: Robert P. J. Day
>> Cc: Rifenbark, Scott M; yocto@yoctop
ginal Message-
>From: Burton, Ross [mailto:ross.bur...@intel.com]
>Sent: Monday, June 24, 2013 7:57 AM
>To: Robert P. J. Day
>Cc: Rifenbark, Scott M; yocto@yoctoproject.org
>Subject: Re: [yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>On
On 24 June 2013 15:47, Robert P. J. Day wrote:
> On Mon, 24 Jun 2013, Rifenbark, Scott M wrote:
>
>> What I was trying to convey here is that oe-init-build-env draws on
>> some files in the meta-yocto layer. The script oe-init-build-env is
>> in the poky repository (or refered to as "Source Direc
On Mon, 24 Jun 2013, Rifenbark, Scott M wrote:
> What I was trying to convey here is that oe-init-build-env draws on
> some files in the meta-yocto layer. The script oe-init-build-env is
> in the poky repository (or refered to as "Source Directory" in the
> documentation). The sample files are i
: Re: [yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>On 06/23/2013 11:52 PM, Rifenbark, Scott M wrote:
>> Hi,
>>
>> I am going to start throwing these diagrams out to the mailing list
>and see if I can get any feedback. This at
about layers and their role
regarding what they feed into the whole process.
Thanks,
Scott
From: Jerrod Peach [mailto:pea...@lexmark.com]
Sent: Monday, June 24, 2013 6:00 AM
To: Rifenbark, Scott M
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Documenting YP Development Environment in more d
On 24 June 2013 13:59, Jerrod Peach wrote:
> auto.conf (That's not even present in my 1.4 workspace. Is this going to be
> something new in 1.5?)
auto.conf is read along with site.conf and local.conf, and is intended
to be automatically created and maintained by autobuilders. That's
why you don
On 06/23/2013 11:52 PM, Rifenbark, Scott M wrote:
> Hi,
>
> I am going to start throwing these diagrams out to the mailing list and see
> if I can get any feedback. This attached figure dives into user
> configuration. Any and all discussion, correction, suggestions are welcome.
It appears
Scott,
I think the general diagram looks pretty good, although I'd argue there's a
little too much detail in the file list being shown, or else some of this
new stuff is going to be useful in 1.5 when it's not doing anything in 1.4.
Here are the files I see as excessive:
In meta-yocto:
- loc
Hi Rudi,
On 24 June 2013 01:41, Rudolf Streif wrote:
>> If I were writing a book about Yocto/OE,
> This is a project I am currently working on, a book about the Yocto Project.
Awesome! That's great news! I was hoping someone would "beat me to it"
:-) I look forward to reading it once it's done.
On Mon, Jun 24, 2013 at 1:41 AM, Rudolf Streif
wrote:
> Hi Trever et al:
>
>
>>
>> If I were writing a book about Yocto/OE,
>
>
> This is a project I am currently working on, a book about the Yocto Project.
> The goal is to enable readers to do practical projects with YP. As the
> subject matter f
Hi Trever et al:
> If I were writing a book about Yocto/OE,
This is a project I am currently working on, a book about the Yocto
Project. The goal is to enable readers to do practical projects with YP. As
the subject matter for the project described in the book I have chosen a
home automation p
Hi,
I am going to start throwing these diagrams out to the mailing list and see if
I can get any feedback. This attached figure dives into user configuration.
Any and all discussion, correction, suggestions are welcome.
Scott
>-Original Message-
>From: Rifenbark, Scott M
>Sent: Fri
On 23 June 2013 00:01, Trevor Woerner wrote:
> Has anyone else heard of vimcasts.org?
http://vimcasts.org/episodes/archive
is a good example of what I'm thinking about.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/li
Has anyone else heard of vimcasts.org?
Short, concise, detailed screen-casts of specific Yocto tasks coupled
with "show notes", I think, would be an awesome other way of
delivering this information.
yoctocasts.org anyone?
___
yocto mailing list
yocto@yo
Coincidentally, Nicolas and I were recently involved in providing a
whirlwind tour of Yocto/OE to some developers last week.
On 20 June 2013 04:40, Rifenbark, Scott M wrote:
> We can get started now on this by starting to define details for some obvious
> points or large areas of the flow. What
I think this is an excellent project and am excited to see it coming together.
Are the meetings open for participation? I can't guarantee that I'd be
available when you run them, but I wouldn't mind listening in if I am.
If I were writing a book about Yocto/OE, in the first chapter I would
have t
leton; Osier-mixon, Jeffrey
> Subject: Re: [yocto] Documenting YP Development Environment in more
> detail
>
>
>
> On 6/20/13 8:23 AM, "Rifenbark, Scott M"
> wrote:
>
> >
> >
> >>-Original Message-
> >>From: yocto-boun.
ie
>>Cc: yocto@yoctoproject.org; Paul Eggleton; Osier-mixon, Jeffrey
>>Subject: Re: [yocto] Documenting YP Development Environment in more
>>detail
>>
>>On Thu, Jun 20, 2013 at 10:25 AM, Richard Purdie
>> wrote:
>>> On Thu, 2013-06-20 at 09:49
yocto] Documenting YP Development Environment in more
>detail
>
>On Thu, Jun 20, 2013 at 10:25 AM, Richard Purdie
> wrote:
>> On Thu, 2013-06-20 at 09:49 -0400, Bruce Ashfield wrote:
>>> On 13-06-20 04:40 AM, Rifenbark, Scott M wrote:
>>> > Hi,
>>> >
On Thu, Jun 20, 2013 at 10:25 AM, Richard Purdie
wrote:
> On Thu, 2013-06-20 at 09:49 -0400, Bruce Ashfield wrote:
>> On 13-06-20 04:40 AM, Rifenbark, Scott M wrote:
>> > Hi,
>> >
>> > Recently, Paul, Ross, Richard and I had a video conference meeting where
>> > we had some initial discussion on
On 13-06-20 10:25 AM, Richard Purdie wrote:
On Thu, 2013-06-20 at 09:49 -0400, Bruce Ashfield wrote:
On 13-06-20 04:40 AM, Rifenbark, Scott M wrote:
Hi,
Recently, Paul, Ross, Richard and I had a video conference meeting where we had some initial
discussion on how to satisfy YOCTO #2808 (https
On Thu, 2013-06-20 at 09:49 -0400, Bruce Ashfield wrote:
> On 13-06-20 04:40 AM, Rifenbark, Scott M wrote:
> > Hi,
> >
> > Recently, Paul, Ross, Richard and I had a video conference meeting where we
> > had some initial discussion on how to satisfy YOCTO #2808
> > (https://bugzilla.yoctoproject.o
On 13-06-20 04:40 AM, Rifenbark, Scott M wrote:
Hi,
Recently, Paul, Ross, Richard and I had a video conference meeting where we had some initial
discussion on how to satisfy YOCTO #2808 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=2808),
which calls for an illustration showing source and
Hi,
Recently, Paul, Ross, Richard and I had a video conference meeting where we had
some initial discussion on how to satisfy YOCTO #2808
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=2808), which calls for an
illustration showing source and destination directories during a build using
Y
42 matches
Mail list logo
