From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc.
Date: Sun, 8 Jul 2012 13:59:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207081227430.27741@oneiric> (raw)
(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?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2012-07-08 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 17:59 Robert P. J. Day [this message]
2012-07-09 9:05 ` more pedantry -- looking to clarify layers definition, BBPATH, BBFILES, etc 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
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.1207081227430.27741@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