Dave, Thanks for the comments and the suggestions. I think the color/style convention is a good idea. I will play around with that. I will also not that fact about the build directory.
Scott >-----Original Message----- >From: Stewart, David C >Sent: Tuesday, July 09, 2013 6: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" <scott.m.rifenb...@intel.com> >wrote: > >>Here is a link to draft section on the user configuration block of the >YP >>Development Environment work. Check this out and provide feedback for >>appropriate level of detail, usefulness, missing info, ect. This draft >>section, once we settle on it, will set the tone and level for the >>remaining detailed sections that make up the general environment >diagram. >> >> >>http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#a- >closer-l >>ook-at-the-yocto-project-development-environment > >I think it will look really good. > >Would it make sense to adopt some kind of notation for when a directory >is >a "source" vs "destination" type directory? For example, in the diagram >you have there, maybe color the source and destination directory boxes >differently or use hashed lines vs solid? Not sure it will be clear or >confusing once you get into more examples. > >Also, it's a nit, but I think oe-init-build-env only creates the Build >Directory if it doesn't already exist. > >> >>Thanks, >>Scott >> >>>-----Original Message----- >>>From: yocto-boun...@yoctoproject.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 configuration >>> >>>On 25 June 2013 01:39, Philip Balister <phi...@balister.org> 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 >>>uses a custom tool (combo-layer, in oe-core/scripts) to merge the >>>layers into a single repo. You could also use git submodules to make >>>a single repo (such as Guacamayo), or git subtree merges, or use repo >>>(gumstix), or have a script that manages the fetching of multiple >>>layers (Angstrom). >>> >>>Ross >>>_______________________________________________ >>>yocto mailing list >>>yocto@yoctoproject.org >>>https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto