On Fri, Apr 23, 2010 at 10:29:54PM +0200, Koen Kooi wrote: > >> 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. > > I don't think we can make it "universal" without sacrificing key benefits. > > > 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. > > The immediate problem I'm trying to address now is that having both an > armv5te and armv7a toolchain installed is breaking horribly. Ideally > they would coexist peacefully, but I don't know if we can manage that, > without impacting the ease of use.
I know it's not what you are looking for, but easier workaround would be to install different toolchains in different paths... :) -- Denys _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
