From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: more BSP Guide pedantry involving customizing a recipe
Date: Tue, 30 Dec 2014 15:48:32 -0700 [thread overview]
Message-ID: <54A32BC0.3090102@mlbassoc.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1412301427370.12620@localhost>
On 2014-12-30 12:31, Robert P. J. Day wrote:
>
> (you can tell i'm bored and want to get back up to speed on stuff
> ...)
>
> section 1.4 in BSP Guide, "Customizing a Recipe for a BSP", appears
> to discuss a new layer, "meta-xyz", then suggests the new "interfaces"
> file for this machine needs to go at the location:
>
> meta-xyz/recipes-core/init-ifupdown/files/xyz/interfaces
> ^^^ ???
>
> but the files/ subdirectory of "xyz/" would appear to be necessary
> (as we all know) only if this was a more general layer that
> represented several machines (say, meta-ti) for which we *needed* to
> distinguish between machines.
>
> so while the above might be technically correct, it might mislead
> readers to think they *needed* to create a "xyz/" subdirectory for
> that overriding interfaces file.
Actually, it *is* necessary if meta-xyz supports more than one
MACHINE and those targets have unique versions of the 'interfaces'
file (which is common since this file is being tailored for a
particular target machine)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-12-30 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 19:31 more BSP Guide pedantry involving customizing a recipe Robert P. J. Day
2014-12-30 22:48 ` Gary Thomas [this message]
2014-12-30 23:37 ` Gary Thomas
2014-12-31 10:06 ` Robert P. J. Day
2015-01-05 23:42 ` Rifenbark, Scott M
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=54A32BC0.3090102@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.