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
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 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
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 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
roject.org
>> Subject: Re: [yocto] Documenting YP Development Environment in more
>> detail - user configuration
>>
>> 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 conve
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,
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
21 matches
Mail list logo
