All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: managing layer priorities
Date: Mon, 09 Apr 2012 14:58:49 +0100	[thread overview]
Message-ID: <4F82EB19.9040207@r-finger.com> (raw)
In-Reply-To: <4F82DE49.4060408@mlbassoc.com>

On 09/04/12 14:04, Gary Thomas wrote:
> On 2012-04-09 00:18, Tomas Frydrych wrote:
>> On 08/04/12 23:28, Tomas Frydrych wrote:
>>> Is there a way to change the priority that a layer assigns itself in its
>>> layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
>>> want it to have a lower priority than the latter. Currently meta-yocto
>>> gives itself "5" and meta-oe "6", I'd like to change this without having
>>> to modify meta-oe/conf/layer.conf, but can't find a way to do this.
>>
>> Never mind, it is possible to override these in the last layer listed in
>> BBLAYERS.
> 
> How so?

You can set the various BBFILE_PRIORITY_**** and other variables in the
layer.conf for the last layer listed in your bblayers.conf. The layer
priorities get evaluated only after all of the layer.conf files have
been parsed, so anything that is set in the last layer.conf will be the
final value. I use the Yocto model where (unlike with OE layers) the
layer.conf prepends its layer path to BBPATH, so my custom layer is
last, but I imagine it would be possible to create a fake layer with no
recipes just for this specific purpose.

Tomas

> 



  reply	other threads:[~2012-04-09 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08 22:28 managing layer priorities Tomas Frydrych
2012-04-09  6:18 ` Tomas Frydrych
2012-04-09 13:04   ` Gary Thomas
2012-04-09 13:58     ` Tomas Frydrych [this message]
2012-04-09 14:09       ` Paul Eggleton
2012-04-09 14:53         ` Tomas Frydrych

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=4F82EB19.9040207@r-finger.com \
    --to=tf+lists.yocto@r-finger.com \
    --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.