From: Christopher Larson <kergoth@gmail.com>
To: Joshua Immanuel <josh@hipro.co.in>
Cc: yocto@yoctoproject.org
Subject: Re: overriding a class in custom layer
Date: Tue, 24 Jan 2012 07:32:47 -0700 [thread overview]
Message-ID: <2F85497E73304B2B8FBE56AEEDEEA234@gmail.com> (raw)
In-Reply-To: <1327415044.17885.7.camel@babel.joshhome>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Tuesday, January 24, 2012 at 7:24 AM, Joshua Immanuel wrote:
> Hello Christopher,
>
> Thanks for the reply.
>
> On Tue, 2012-01-24 at 07:07 -0700, Christopher Larson wrote:
> > Ensure that your layer is before the other in BBLAYERS.
>
>
> As you mentioned reordering BBLAYERS to have my custom layer before
> 'meta' layer solved the issue. I was of the notion that setting
> BBFILE_PRIORITY higher for my layer would be sufficient.
>
>
Unfortunately, BBFILE_PRIORITY only affects the choice of what *recipes* to use between the different layers, not config files or classes. The latter are found via BBPATH, which is incrementally appended to by each layer.conf. This separation is unfortunate, as it means part of the layer priority is in the user's hands (or the script generating bblayers.conf, if using one), and part is in the layers' hands (layer.conf), but that's the way it is for now.
--
Christopher Larson
[-- Attachment #2: Type: text/html, Size: 1386 bytes --]
next prev parent reply other threads:[~2012-01-24 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 10:47 overriding a class in custom layer Joshua Immanuel
2012-01-24 14:07 ` Christopher Larson
2012-01-24 14:24 ` Joshua Immanuel
2012-01-24 14:32 ` Christopher Larson [this message]
2012-01-24 16:17 ` Paul Eggleton
2012-01-24 16:19 ` Christopher Larson
2012-01-25 5:33 ` Joshua Immanuel
2012-01-25 15:56 ` Paul Eggleton
2012-01-25 17:04 ` Chris Larson
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=2F85497E73304B2B8FBE56AEEDEEA234@gmail.com \
--to=kergoth@gmail.com \
--cc=josh@hipro.co.in \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.