[yocto] Layer input

[Jerrod Peach]

Scott,

Getting closer to what I was thinking, but I still have a couple questions,
primarily regarding the BSP layer.

   - There are still a few references to <name>.  Shouldn't those also be
   <recipe>?
   - I'm still confused by the presence of all the specifically-named
   recipes-* directories.  I tried running yocto-layer and I didn't get any of
   those present.  I couldn't find the bsp-layer tool, but I'll grant I didn't
   search really hard.  (I only checked out master of poky and searched around
   a bit.)  What's making you want to put them all in this diagram?

Also, it strikes me that bblayers.conf needs to show up in this diagram
somewhere, I think, since it controls what layers bitbake sees.

Kind regards,

Jerrod


On Thu, Jun 27, 2013 at 3:41 AM, Rifenbark, Scott M <
scott.m.rifenbark at intel.com> wrote:

>  Hi, ****
>
> ** **
>
> I have tweaked this figure some based on Bruce and Jerrod’s input.  To
> help me figure out some of the basics, I ran the yocto-layer and bsp-layer
> scripts to create a general and BSP layer, respectively.  Please look over
> the contents of these layers and comment.  General comments on the whole
> concept of how I am presenting the layers are welcome along with any other
> observations.  ****
>
> ** **
>
> Thanks, ****
>
> Scott****
>
> ** **
>
> *From:* Jerrod Peach [mailto:peachj at lexmark.com]
> *Sent:* Tuesday, June 25, 2013 11:07 AM
>
> *To:* Rifenbark, Scott M
> *Cc:* yocto at yoctoproject.org; Paul Eggleton
> *Subject:* Re: [yocto] Layer input****
>
>  ** **
>
> Scott,****
>
>    - Distro Layer****
>
>
>     - I'm unclear on what <name> is.  Is that supposed to be <distro>?
>        <recipe>?  It probably shouldn't just be <name>, should it?****
>
>
>    - Software Layer****
>
>
>     - Should COPYING.MIT just be COPYING to be more generically
>       applicable?****
>       - conf/<layer_name>.conf should be just layer.conf, right?****
>
>
>    - BSP Layer****
>
>
>     - COPYING.MIT file again.****
>       - machine/<name>.conf should probably be machine/<machine*>.conf.
>        You can probably drop the non-asterisk version, since an asterisk implies,
>       "There might be more stuff, there might not."****
>       - recipes-bsp/formfactor shouldn't also have another formfactor
>       directory, should it?  Or is the "files" directory in 1.4 replaced with
>       another formfactor-named directory?  Also, <name> should be <machine> again.
>       ****
>       - What's everything from recipes-core down?  I can buy
>       recipes-kernel being in a bsp, but are any other directories really
>       necessary?****
>
>  Kind regards,****
>
> ** **
>
> Jerrod****
>
> ** **
>
> On Tue, Jun 25, 2013 at 8:35 AM, Rifenbark, Scott M <
> scott.m.rifenbark at intel.com> wrote:****
>
> Hi,
>
> This next illustration attempting to dive deeper in the YP Development
> Process takes the remaining left-side input from that figure in the Quick
> Start (metadata, Machine, and Policy).  Note that when the original figure
> was created that appears in the QS, the layer stuff had not yet been
> established.  This figure I am attaching is rough.  I am unsure as to the
> contents of these layers.  Right now it is detailed but with generic names.
>  The idea is that individual layers are preferred to do things such as
> provide software, configure policy, and configure machines.  I am including
> some notes at the bottom of the figure that would not be part of the figure
> but might help to get across what I am trying to accomplish here.
>
> Any suggestions and feedback is really appreciated.
>
> Thanks,
> Scott
>
> Scott Rifenbark
> Intel Corporation
> Yocto Project Documentation
> 503.712.2702
> 503.341.0418 (cell)
>
>
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130627/b20a8943/attachment.html>