Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc.
Date: Mon, 9 Jul 2012 11:28:40 +0200	[thread overview]
Message-ID: <20120709092840.GB6308@jama.jama.net> (raw)
In-Reply-To: <20120709092332.GA6308@jama.jama.net>

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

On Mon, Jul 09, 2012 at 11:23:32AM +0200, Martin Jansa wrote:
> On Sun, Jul 08, 2012 at 01:59:48PM -0400, Robert P. J. Day wrote:
> > 
> >   (most of this is sort of self-evident but it's not documented as
> > well as it could be so i just want to make sure i have it exactly
> > right.)
> > 
> >   snippets of some layer.conf files:
> > 
> > oe-core:
> > 
> > BBPATH .= ":${LAYERDIR}"
> > BBFILES += "${LAYERDIR}/recipes-*/*/*.bb"
> > 
> > meta-hob:
> > 
> > BBPATH := "${BBPATH}:${LAYERDIR}"
> > BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb"
> > 
> > meta-yocto:
> > 
> > BBPATH := "${LAYERDIR}:${BBPATH}"
> > BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
> >             ${LAYERDIR}/recipes-*/*/*.bbappend"
> > 
> >   note how meta-hob *appends* itself to BBPATH, while meta-yocto
> > *prepends* itself.  is there no possibility that this will cause some
> > confusion based on how BBPATH is used to resolve the location of class
> > or conf files?  i realize you should try to avoid that sort of
> > conflict but it still seems possible that someone might choose the
> > names of some files badly and the unpredictable ordering in BBPATH
> > will cause grief, no?
> 
> Yes, order is important and prepending makes it harder for person
> writting bblayers.conf to influence it:
> 
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/024914.html
> 
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-February/018115.html:
> BBFILE_PRIORITY controls recipe priority. BBLAYERS order controls
> BBPATH order which in turn controls bbclass/config priority, as things
> stand today.
> 
> See also this thread for more details:
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-May/032387.html

And this one
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-August/007387.html

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2012-07-09  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 17:59 more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc Robert P. J. Day
2012-07-09  9:05 ` Andrei Gherzan
2012-07-09 20:34   ` Robert P. J. Day
2012-07-09 20:37     ` Andrei Gherzan
2012-07-09 21:23     ` Paul Eggleton
2012-07-09 22:48       ` Robert P. J. Day
2012-07-09  9:23 ` Martin Jansa
2012-07-09  9:28   ` Martin Jansa [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=20120709092840.GB6308@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox