From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc.
Date: Mon, 09 Jul 2012 22:23:59 +0100 [thread overview]
Message-ID: <2863878.hMO01FTXta@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1207091630380.24097@oneiric>
On Monday 09 July 2012 16:34:20 Robert P. J. Day wrote:
> On Mon, 9 Jul 2012, Andrei Gherzan wrote:
> > 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?
To avoid confusion, layer priorities are only applicable with regard to
recipes/bbappends. To respond to your question, if two layers have the same
priority (which is legal) then if there is a situation where a recipe file is
provided by both layers, which one "wins" will depend on the order they appear
in bblayers.conf.
The BBPATH variable is completely independent of this, and is the path that is
used to find conf and bbclass files; however, the order in which the appends /
prepends will be applied is of course the order in which they are parsed,
which is the order in which they appear in bblayers.conf. Most layers should
be appending to BBPATH rather than prepending but there may be exceptions.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-09 21:35 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 [this message]
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=2863878.hMO01FTXta@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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