All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: discussion of layers in dev manual uses a *really* bad example
Date: Tue, 01 Jan 2013 10:58:06 -0800	[thread overview]
Message-ID: <50E331BE.1020302@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212300440460.11647@oneiric>

On 12/30/2012 01:45 AM, Robert P. J. Day wrote:
>
>    more pedantry -- dev manual, section 5.1.2 talks about creating a
> new layer and recommends using the meta-yocto layer.conf as a starting
> point, which contains:
>
>       # We have a conf and classes directory, add to BBPATH
>       BBPATH := "${LAYERDIR}:${BBPATH}"
>
>    the problem is that almost every other layer *appends* LAYERDIR to
> BBPATH, not the other way around, so that example is spectacularly
> unrepresentative.  (i'm unaware of any other layer that sets BBPATH in
> that order, and i recall tom zanussi (?) explaining once why that
> was.)
>
>    perhaps a different example, and a short explanation about why the
> meta-yocto layer is the exception here?

ScottR:

As some background on this issue, please take a look at this thread from 
almost exactly a month ago:

https://lists.yoctoproject.org/pipermail/yocto/2012-December/013041.html

https://lists.yoctoproject.org/pipermail/yocto/2012-December/013057.html

I agree that we shouldn't recommend using the meta-yocto layer.conf as a 
starting point, due to the BBPATH append ordering difference.

And maybe a note about why we order the BBPATH append as we do in 
meta-yocto (see Thomas' concise explanation in the second link above) 
would be appropriate.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


      reply	other threads:[~2013-01-01 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30  9:45 discussion of layers in dev manual uses a *really* bad example Robert P. J. Day
2013-01-01 18:58 ` Scott Garman [this message]

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=50E331BE.1020302@intel.com \
    --to=scott.a.garman@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.