From: Philip Balister <philip@balister.org>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Documenting YP Development Environment in more detail - user configuration
Date: Mon, 24 Jun 2013 12:55:40 -0400 [thread overview]
Message-ID: <51C87A0C.1050003@balister.org> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF514E7@ORSMSX101.amr.corp.intel.com>
On 06/24/2013 11:08 AM, Rifenbark, Scott M wrote:
> 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.
Actually, the script is in two places, the root level of a poky checkout
and in the oe-core directory.
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.
Philip
>
> Scott
>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@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 24 June 2013 15:47, Robert P. J. Day <rpjday@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
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
next prev parent reply other threads:[~2013-06-24 16:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 3:52 Documenting YP Development Environment in more detail - user configuration Rifenbark, Scott M
2013-06-24 12:59 ` Jerrod Peach
2013-06-24 14:08 ` Burton, Ross
2013-06-24 14:12 ` Rifenbark, Scott M
2013-06-24 13:15 ` Philip Balister
2013-06-24 14:27 ` Rifenbark, Scott M
2013-06-24 14:47 ` Robert P. J. Day
2013-06-24 14:57 ` Burton, Ross
2013-06-24 15:08 ` Rifenbark, Scott M
2013-06-24 16:55 ` Philip Balister [this message]
2013-06-24 16:59 ` Burton, Ross
2013-06-24 18:25 ` Philip Balister
2013-06-24 18:37 ` Jeff Osier-Mixon
2013-06-25 0:39 ` Philip Balister
2013-06-25 4:58 ` Rifenbark, Scott M
2013-06-25 9:54 ` Burton, Ross
2013-07-09 5:54 ` Rifenbark, Scott M
2013-07-09 13:51 ` Stewart, David C
2013-07-09 14:23 ` Rifenbark, Scott M
2013-06-24 17:00 ` Rifenbark, Scott M
2013-06-28 19:58 ` Khem Raj
2013-06-29 4:50 ` Rifenbark, Scott M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51C87A0C.1050003@balister.org \
--to=philip@balister.org \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.