All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:15:27 -0400	[thread overview]
Message-ID: <51C8466F.8040808@balister.org> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF5130F@ORSMSX101.amr.corp.intel.com>

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 the diagram says that the oe-init-build-env script creates
the files in the users conf dir from the meta-yocto layer. These files
(and the script) are in meta. This diagram creates the misleading idea
that the meta-yocto layer is mandatory in order to create a working build.

Philip

> 
> Scott
> 
>> -----Original Message-----
>> From: Rifenbark, Scott M
>> Sent: Friday, June 21, 2013 1:22 AM
>> To: Paul Eggleton; Burton, Ross
>> Subject: user configuration
>>
>> Paul and Ross,
>>
>> Attached is a sample figure that focuses on "User Configuration."  The
>> illustration attempts to reveal where user configuration data comes from
>> and what processes and user-driven commands are related to it.  Right
>> now, BitBake is simply a box.
>>
>> If you can, give me some comments on this.  I would like to hear on
>> level of detail as well as technical accuracy.
>>
>> Thanks,
>> Scott
>>
>> Scott Rifenbark
>> Intel Corporation
>> Yocto Project Documentation
>> 503.712.2702
>> 503.341.0418 (cell)
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 


  parent reply	other threads:[~2013-06-24 13:15 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 [this message]
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
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=51C8466F.8040808@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.