From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] allarch.bbclass: Set FEED_ARCH to original value of BASE_PACKAGE_ARCH and then set BASE_PACKAGE_ARCH to 'all'
Date: Wed, 15 Jun 2011 11:22:02 +0100 [thread overview]
Message-ID: <1308133322.15712.395.camel@rex> (raw)
In-Reply-To: <9B8FDB01-CFAA-497E-BD0E-93D421E6C4F8@dominion.thruhere.net>
On Wed, 2011-06-15 at 12:15 +0200, Koen Kooi wrote:
> Op 15 jun 2011, om 12:07 heeft Richard Purdie het volgende geschreven:
> > Well, I was trying to provide some hints as to how we might be able to
> > improve this situation, not write the whole roadmap. From what I
> > remember and the quick discussion we had offlist there are two things
> > FEED_ARCH tries to do:
> >
> > a) Provide an addition to overrides that represents the
> > optimisation/tune profile being used (like armv7a).
> >
> > b) Provide some info in BASE_PACKAGE_ARCH so that when PACKAGE_ARCH is
> > overwritten, you can still find out what it would have been set to.
> >
> > For a), we could update the common include files for the omap/armv7a
> > platforms and append to MACHINEOVERRIDES there with the appropriate
> > entries
>
> It's not omap specific, you really need have access to the arch in
> overrides for *all* platforms. I'm using armv7a is an example since
> angstrom does TARGET_FPU_armv7a = "hard", but it also does that for
> various powerpc architectures.
I'm also using omap as an example. I'd imagine the powerpc bits would
also work from a common small set of tune include files though? I
suspect the Intel guys would love some way to say "x86" instead of
"i386|i486|i586|i686" etc. so this is a general problem.
>
> And any change like this would need to get propagated to all the
> machine layers out there as well, unlike .dev where everything was in
> one place.
I know, but we have two choices:
a) Continue this spiral of confusing variable names, conflict and wacky
bugs
b) Come up with a plan to address it and roll it out
I'm favouring b), particularly since this would help several different
architectures with a variety of issues. If we need to better document
that and have a process fine, but that is not a good argument for not
doing it at all.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-15 10:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 21:13 [PATCH V2] allarch.bbclass: Set FEED_ARCH to original value of BASE_PACKAGE_ARCH and then set BASE_PACKAGE_ARCH to 'all' Khem Raj
2011-06-14 21:18 ` Koen Kooi
2011-06-14 21:24 ` Richard Purdie
2011-06-14 21:32 ` Khem Raj
2011-06-14 21:33 ` Koen Kooi
2011-06-14 21:39 ` Khem Raj
2011-06-14 21:32 ` Koen Kooi
2011-06-14 21:40 ` Khem Raj
2011-06-14 21:44 ` Koen Kooi
2011-06-14 23:12 ` Khem Raj
2011-06-15 7:00 ` Koen Kooi
2011-06-15 10:16 ` Richard Purdie
2011-06-15 10:18 ` Koen Kooi
2011-06-15 10:23 ` Richard Purdie
2011-06-15 15:28 ` Khem Raj
2011-06-15 10:07 ` Richard Purdie
2011-06-15 10:15 ` Koen Kooi
2011-06-15 10:22 ` Richard Purdie [this message]
2011-06-15 10:37 ` Koen Kooi
2011-06-15 11:36 ` Richard Purdie
2011-06-15 11:52 ` Koen Kooi
2011-06-15 15:29 ` Mark Hatle
2011-06-15 8:56 ` Koen Kooi
2011-06-15 9:33 ` Richard Purdie
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=1308133322.15712.395.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox