Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: more pedantry: inconsistent presentation of how to introduce layers
Date: Tue, 24 Jul 2012 10:43:21 +0100	[thread overview]
Message-ID: <1906764.DupgyPkgTn@helios> (raw)
In-Reply-To: <CA+chaQdQwBe9Z7Np9fqGXGbC1Ghe9MFAP0E2vOFEM-MiTWb4eg@mail.gmail.com>

On Tuesday 24 July 2012 11:29:26 Martin Jansa wrote:
> > As I mentioned before, the priority currently has no bearing on the order
> > of BBPATH - that is determined by the order in which the layer conf files
> > are parsed and (as you highlight) whether they prepend or append to
> > BBPATH. Remember that the BBPATH only affects how class and conf files
> > are found - it does not have anything to do with recipes.
> 
> And order of .bbappends applied, no? In case some recipe has
> .bbappends in multiple layers and
> later layer is trying to override some setting which is also altered
> by some bbappend in layer between.

No. The order of bbappend application is layer priority order, or if bbappends 
for the same recipe are in layers with the same layer priority, the order is 
the order in which the layers are parsed (= the order in which the layers 
appear in bblayers.conf).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-07-24  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  9:04 more pedantry: inconsistent presentation of how to introduce layers Robert P. J. Day
2012-07-24  9:15 ` Paul Eggleton
2012-07-24  9:20   ` Paul Eggleton
2012-07-24  9:25   ` Robert P. J. Day
2012-07-24  9:29   ` Martin Jansa
2012-07-24  9:43     ` Paul Eggleton [this message]

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=1906764.DupgyPkgTn@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --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