From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: BBFILE_PRIORITY confusion
Date: Sun, 21 Nov 2010 04:13:17 -0700 [thread overview]
Message-ID: <4CE8FECD.5050905@mlbassoc.com> (raw)
I'm building a multi-layered system, something like this:
meta-manufacturer/...
meta-platform/...
The idea is that we'll put any packages and support that are
useful for all platforms we make in meta-manufacturer/ and only
target platform specifics in meta-platform/
I had set BBFILE_PRIORITY=6 in meta-manufacturer/ and 7 in meta-platform/
Here's the confusion. I originally had something like this for our internal
kernel packages:
meta-manufacturer/packages/linux/linux-manufacturer_2.6.32.bb
meta-platform/packages/linux/linux-manufacturer_2.6.28.bb
This was due to the fact that some other platform we make is already
using 2.6.32, but we still have some back at 2.6.28
Today, I tried to bring one of those platforms to 2.6.32, so I added
this (exactly as I have done for other platforms already running 2.6.32):
meta-platform/packages/linux/linux-manufacturer_2.6.32.bbappend
initially leaving the linux-manufacturer_2.6.28.bb in place.
Much to my surprise, bitbake/poky never even reads the linux-manufacturer_2.6.32.bbappend
file! This seems to be related to BBFILE_PRIORITY - when I swapped the
priorities around, it started to work. While this gets me moving, I think
it's wrong - I may need at some point for this platform to be able to override
some manufacturer recipe, etc.
It seems to me that BBFILE_PRIORITY is a bit too zealous; barring any other
constraint, I should think that the 2.6.32 recipe should always take precedence.
Am I missing something here, or is it a bug?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2010-11-21 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 11:13 Gary Thomas [this message]
2010-11-22 13:53 ` BBFILE_PRIORITY confusion Joshua Lock
2010-11-22 15:33 ` Richard Purdie
2010-11-22 15:37 ` Gary Thomas
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=4CE8FECD.5050905@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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