On 7/8/13 10:54 PM, "Rifenbark, Scott M" <firstname.lastname@example.org>
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.
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.
From: email@example.com [mailto:yocto-
firstname.lastname@example.org] On Behalf Of Burton, Ross
Sent: Tuesday, June 25, 2013 2:55 AM
To: Philip Balister
Subject: Re: [yocto] Documenting YP Development Environment in more
detail - user configuration
On 25 June 2013 01:39, Philip Balister <email@example.com> wrote:
I totally agree we drifted way beyond the initial discussion of theIs there such a thing as a "typical" use of oe-core + layers? Poky
figure. The key thought here is understanding how Poky differs from a
typical use of oe-core + other layers.
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
yocto mailing list