On Fri, 2011-07-22 at 10:03 -0500, Kumar Gala wrote: > On Jul 22, 2011, at 9:49 AM, Richard Purdie wrote: > > > There is currently consideradble confusion over how the tune files operate > > and how these interact with the rest of the build system. This > > update/overhaul > > changes things so the tune files are primarily resonsible for setting: > > > > TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that > > represents the architecture we're targetting. > > > > TUNE_PKGARCH - The value that represents the tune confuration that this set > > of tune parameters results in. > > > > This allows the significant improvement that the core can now always > > determine > > the target architecture value, even when TARGET_ARCH needs to be reset to > > something different and likewise, there is one package architecture variable > > the core can reference allowing simplification of the BASE_PACKAGE_ARCH, > > PACKAGE_ARCH > > and FEED_ARCH variables. > > > > Signed-off-by: Richard Purdie <[email protected]> > > --- > > Can you give an example of how this will work for multilib?
These are setting the scene for multilib, it doesn't directly enable it. For an example of the end result see this branch: http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/oe-core/ml but this isn't in a form suitable for submission yet which is what I'm working towards. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
