All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	Gary Thomas <gary@mlbassoc.com>
Subject: Re: Incorrect FILESPATH usages
Date: Sun, 07 Apr 2013 00:39:03 +0100	[thread overview]
Message-ID: <1774512.QpcBWiQjzK@helios> (raw)
In-Reply-To: <CABcZANnh=K=H-gGFbTTHH0hJsxyK_F+m4Z7k1oFZ2=+wzFbFBg@mail.gmail.com>

On Saturday 06 April 2013 15:14:20 Chris Larson wrote:
> On Sat, Apr 6, 2013 at 5:17 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> > I have run across a problem where a main recipe is written in
> > such a way that makes using .bbappend impossible.  This happens
> > if the main recipe has an explicit assignment for FILESPATH.
> > In this case, the .bbappend is unable to add to that path, e.g.
> > to add a machine specific patch, etc.
> 
> If the explicit definition calls base_set_filespath, then FILESEXTRAPATHS
> can still be used.

Also a number of the examples given are using .= which should also be 
acceptable and won't interfere with FILESEXTRAPATHS usage in bbappends. 
However the ones that just assign it to a value without base_set_filespath - 
especially when they're covering directories that are already handled by the 
default value of FILESPATH - should be removed.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2013-04-06 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 12:17 Incorrect FILESPATH usages Gary Thomas
2013-04-06 22:14 ` Chris Larson
2013-04-06 23:39   ` 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=1774512.QpcBWiQjzK@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=gary@mlbassoc.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 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.