[oe] [RFC][PATCH] meta-toolchain: use MULTIMACH_TARGET_SYS instead of TARGET_SYS

Tom Rini tom_rini at mentor.com
Fri Apr 23 18:55:59 UTC 2010


On Fri, 2010-04-23 at 20:45 +0200, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 23-04-10 20:22, Denys Dmytriyenko wrote:
> > On Fri, Apr 23, 2010 at 11:07:33AM -0700, Tom Rini wrote:
> >> On Fri, 2010-04-23 at 13:07 +0200, Koen Kooi wrote:
> > Ping
> >>>
> >>> It's better than what we have today, true.  And SDKPATH already contains
> >>> DISTRO, which is the likely changer of TOOLCHAIN_*_TASK.  So...
> >>>
> >>> Acked-by: Tom Rini <tom_rini at mentor.com>
> > 
> >> In general:
> > 
> >> Acked-by: Denys Dmytriyenko <denis at denix.org>
> > 
> >> But, should we then create an arch-specific environment-setup scripts (e.g. 
> >> one for armv4 and another for armv7a, as per your example below)?
> 
> Yes, that needs to be done, as well as seperating the cross tools in
> case different archs need different versions (as is the case with
> angstrom, v5te and v7a need different binutils). This change largely to
> to cosmetically highlight that the toolchain is not really "universal"
> (yet).

And we can talk about if "universal" is really a good goal either.
Taking a bit of a guess in the dark, an SDK with support for all the fun
stuff found on Beagleboard might not be done easily with also having
support for all the fun stuff found on some other ref board too.

I tend to think of these exports as being very board specific, but that
doesn't quite flow with how others think of this stuff, today.

-- 
Tom Rini <tom_rini at mentor.com>
Mentor Graphics Corporation




More information about the Openembedded-devel mailing list