From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: any point in a single machine recipe using a machine-specific file?
Date: Fri, 19 Apr 2013 15:56:54 +0100 [thread overview]
Message-ID: <51715B36.9040408@r-finger.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304191032090.5553@oneiric>
On 19/04/13 15:34, Robert P. J. Day wrote:
> On Fri, 19 Apr 2013, Tomas Frydrych wrote:
>
>> On 19/04/13 15:15, Robert P. J. Day wrote:
>>> i'd wonder, if you're building for a different machine, why are
>>> you including the meta-rpi layer?
>>
>> Because at a distro-level you often want to target different
>> architectures.
>
> yes, i appreciate that but, in *this* case, we're talking about a
> single machine with a single architecture. i'm pretty sure we're
> agreeing, i'm just pointing out that in this specific example, having
> a machine-specific subdirectory is overkill.
BSP layers are not stand alone entities, they can never assume that no
other machines exist in the ecosystem they are pulled into. So, no, it
is most definitely not an overkill. I am not sure how else to explain
it, maybe fix up the RPI layer the way you intended locally and build
yourself a Qemu image, see what happens to your interfaces file.
Tomas
--
http://sleepfive.com
next prev parent reply other threads:[~2013-04-19 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 13:49 any point in a single machine recipe using a machine-specific file? Robert P. J. Day
2013-04-19 14:00 ` Martin Jansa
2013-04-19 14:02 ` Burton, Ross
2013-04-19 14:15 ` Robert P. J. Day
2013-04-19 14:20 ` Tomas Frydrych
2013-04-19 14:34 ` Robert P. J. Day
2013-04-19 14:56 ` Tomas Frydrych [this message]
2013-04-19 14:59 ` Robert P. J. Day
2013-04-19 14:16 ` Tomas Frydrych
2013-04-19 14:23 ` Robert P. J. Day
2013-04-19 14:29 ` Martin Jansa
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=51715B36.9040408@r-finger.com \
--to=tf+lists.yocto@r-finger.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.