From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc.
Date: Mon, 9 Jul 2012 18:48:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207091847540.24998@oneiric> (raw)
In-Reply-To: <2863878.hMO01FTXta@helios>
On Mon, 9 Jul 2012, Paul Eggleton wrote:
> 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.
and that was my basic issue -- that some layers append while others
prepend might cause unexpected behaviour, but i've made my point so
i'll shut up now.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2012-07-09 23:00 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 [this message]
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.1207091847540.24998@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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