[yocto] Documenting YP Development Environment in more detail - user configuration

[Rifenbark, Scott M]

My figure is for Yocto Project documentation so I am going to show that oe-init-build-env gets information from meta-yocto.  I understand that OE-Core sample files are in "meta".  There is a single oe-init-build-env script and it looks in one of two places.

Scott

>-----Original Message-----
>From: Burton, Ross [mailto:ross.burton at intel.com]
>Sent: Monday, June 24, 2013 7:57 AM
>To: Robert P. J. Day
>Cc: Rifenbark, Scott M; yocto at yoctoproject.org
>Subject: Re: [yocto] Documenting YP Development Environment in more
>detail - user configuration
>
>On 24 June 2013 15:47, Robert P. J. Day <rpjday at crashcourse.ca> 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 Directory" in the
>>> documentation).  The sample files are in the meta-yocto layer.  I
>>> thought the meta-yocto layer was needed... maybe I am wrong.  Can I
>>> get more clarification on this?
>>
>>   i regularly build images without any "*yocto*"-named layer, unless
>> i'm misunderstanding the issue here.
>
>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.
>
>Ross