Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
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 16:34:20 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1207091630380.24097@oneiric> (raw)
In-Reply-To: <CAK18fxFD1X6tPLsXG-vwRFu-EeEZDTdeKoTKRYAvYrKJfd-_mQ@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2329 bytes --]

On Mon, 9 Jul 2012, Andrei Gherzan wrote:

>
> On Sun, Jul 8, 2012 at 8:59 PM, Robert P. J. Day <rpjday@crashcourse.ca> 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?
>
>
> I don't think this can cause any problems.

  are you sure?

> It's all about the order the files are searched. As long as you have
> proper priority set nothing can go wrong.

  but what if two or more layers have the same priority?  then what?
it may be that there's no issue here, i'm just pointing out the
possibility that, given the inconsistent way layers add themelves to
BBPATH (either prepending or appending) and the order one lists the
layers in bblayers.conf, is there absolutely no chance that someone
could experience unexpected behaviour given an unusual combination of
circumstances?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2012-07-09 20:45 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 [this message]
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

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=alpine.DEB.2.02.1207091630380.24097@oneiric \
    --to=rpjday@crashcourse.ca \
    --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