From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Adding Custom Files to Build
Date: Thu, 31 Oct 2013 17:16:48 -0600 [thread overview]
Message-ID: <5272E4E0.2060407@mlbassoc.com> (raw)
In-Reply-To: <20131031203257.GK32015@jama>
On 2013-10-31 14:32, Martin Jansa wrote:
> On Thu, Oct 31, 2013 at 01:28:27PM -0700, Leo Schwab wrote:
>> This may seem rather basic, but something that I haven't been able to
>> find any clear discussion on is how to add or modify files in the
>> final rootfs image.
>>
>> We have customized versions of /etc/network/interfaces and
>> /etc/wpa_supplicant.conf, with more to come. Right now I've been
>> adding them by hand to the SD cards, but I would prefer they were
>> added to the rootfs and the .sdcard images as part of the build.
>>
>> I briefly considered creating a .bbappend file to modify the build for
>> the wpa_supplicant.bb recipe, but it turns out that
>> /etc/wpa_supplicant.conf itself comes from a custom file inside the
>> recipe, and it wasn't at all clear how to hook in or override that.
>>
>> I also get the impression that writing a recipe that simply copies
>> stuff to final image will get me yelled at by the build system, since
>> I'm overwriting files already provided by another recipe.
>>
>> Can anyone point me in the right direction?
>
> Creating .bbappends is the right direction, you just need to read a bit
> more docs (hint: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:")
Look at how it's done elsewhere, e.g. meta-raspberrypi or meta-yocto-bsp
for examples of how to provide overrides for your own platform/target/whim.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-10-31 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 20:28 Adding Custom Files to Build Leo Schwab
2013-10-31 20:32 ` Martin Jansa
2013-10-31 23:16 ` Gary Thomas [this message]
2013-11-01 0:54 ` Leo Schwab
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=5272E4E0.2060407@mlbassoc.com \
--to=gary@mlbassoc.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.