All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: How do I use layers to replacing system configuration files?
Date: Sun, 20 Feb 2011 11:27:45 -0700	[thread overview]
Message-ID: <4D615D21.7010304@mlbassoc.com> (raw)
In-Reply-To: <02231D24-6F1D-40B5-BD03-6DAA5A49E038@keylevel.com>

On 02/20/2011 11:23 AM, Chris Tapp wrote:
> On 20 Feb 2011, at 18:04, Gary Thomas wrote:
>
>> You'll need a meta-new/packages/netbase/netbase_4.44.bbappend file which
>> tells bitbake where to find your override files. I do this all the time,
>> for example, I have a board with two targets:
>> $ tree meta-ppc/packages/netbase/
>> meta-ppc/packages/netbase/
>> ├── netbase-4.44
>> │ ├── cobra
>> │ │ ├── interfaces
>> │ └── ppc8379
>> │ ├── interfaces
>> └── netbase_4.44.bbappend
>> $ cat meta-ppc/packages/netbase/netbase_4.44.bbappend
>> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
>> FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
>
> Thanks. I was just looking at .bbappend when your message arrived ;-)
>
> Section 4.8 of the Poky Reference Manual shows an even easier way of doing what I need. All the .bbappend has is:
>
> FILESEXTRAPATHS := "${THISDIR}/${PN}"

That would be great (if it works).  My recipes are based on examples
which were available when the .bbappend and layers were first introduced.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-02-20 18:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 17:58 How do I use layers to replacing system configuration files? Chris Tapp
2011-02-20 18:04 ` Gary Thomas
2011-02-20 18:23   ` Chris Tapp
2011-02-20 18:27     ` Gary Thomas [this message]
2011-02-20 20:10       ` Chris Tapp

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=4D615D21.7010304@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=opensource@keylevel.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.