All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Tobias Olausson <tobias.olausson@pelagicore.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	yocto <yocto@yoctoproject.org>
Subject: Re: bblayer priorities ignored for bbappends?
Date: Wed, 8 Apr 2015 13:23:55 +0200	[thread overview]
Message-ID: <20150408112355.GC2337@jama> (raw)
In-Reply-To: <CAMg8ce8=x06ZsMO=zNxh4P0ZCSdRx5f3Q8L_i=+gMXFzcHOA2Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2573 bytes --]

On Wed, Apr 08, 2015 at 12:29:21PM +0200, Tobias Olausson wrote:
> Hi Paul
> 
> On 8 April 2015 at 10:55, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
> 
> > Hi Tobias,
> >
> > On Wednesday 08 April 2015 08:54:20 Tobias Olausson wrote:
> > > I just had a weird experience with yocto and I wanted to know if the
> > > described behaviour is intentional.
> > >
> > > I have a layer with priority 7 containing a recipe, foo.bb. In another
> > > layer, with priority 8, there is a foo.bbappend. Finally, I just added
> > > another layer, with priority 9, where foo.bb is redefined as a binary
> > > recipe.
> > >
> > > When I added the last layer, I expected that to take precedence over the
> > > other two. However, the bbappend for foo is still applied (which in this
> > > case changed the SRC_URI, making the whole binary recipe moot). Is this
> > > really the way it's supposed to be? I would expect that lower layers
> > cannot
> > > influence layers with higher priority at all, but that does not seem to
> > be
> > > the case.
> >
> > That is the case, yes - bbappends are always applied. As far as I am aware
> > this is the first time this kind of situation has been asked about though
> > so
> > it's probably just that we didn't consider it before.
> >
> 
> I see. I can see a point of always applying bbappends, of course, I had
> just never considered it either.
> 
> 
> >
> > Presumably you could use a bbappend rather than a recipe in the last layer?
> > You might need to stub out some of the functions of course, but it should
> > be
> > possible.
> >
> 
> Indeed, that is a reasonable solution.

It's also possible to use BBMASK to mask bbappends from lower layers in
cases where bbappends are hard/impossible to undo and you cannot easily
convert the recipe in top layer to bbappend (e.g. you don't want to,
because it's different version and lower bbappends are version agnostic
with %).

Regards,

> 
> 
> >
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
> >
> 
> 
> 
> -- 
> Tobias Olausson
> M.Sc
> Software Engineer
> 
> PELAGICORE | Experience Change
> Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden
> Mobile: +46(0)735-873444
> E-Mail: tobias.olausson@pelagicore.com
> IRC: wto @ FreeNode

> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2015-04-08 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  6:54 bblayer priorities ignored for bbappends? Tobias Olausson
2015-04-08  8:55 ` Paul Eggleton
2015-04-08  9:28   ` Nikolay Dimitrov
2015-04-08 10:29   ` Tobias Olausson
2015-04-08 11:23     ` Martin Jansa [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=20150408112355.GC2337@jama \
    --to=martin.jansa@gmail.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=tobias.olausson@pelagicore.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.