2010/7/8 David Greaves <[email protected]>: > On 07/07/10 00:32, Dirk Hohndel wrote: >> >> Again, the default builds that we provide are optimized for Atom - I >> don't think there's anything wrong with that. It's fairly straight >> forward to build for other platforms if you need that, but I think it is >> not a reasonable request that we shouldn't optimize for our platform.
I personally don't think it is unfair that the X86 build off MeeGo.com is optimized for Atom. I mean, the build infrastructure for X86 is sponsored by Intel. That I wouldn't mind if it was iatom as architecture name is another thing. If that was in place, there would be technically no reason why someone couldn't contribute hardware through Linux foundation to add another build target. However. The counterargument to be 'build everything for i486', is that there is no reason why anyone can't set up their own OBS and build Core with their specific optimization flags and get a MeeGo for least-common-denominator X86 needed. Or ARMv4 for that matter (as someone on forum just asked for). Or ARMv6+VFP. Would an unofficial build of MeeGo totally matching Core sources, built for I486 be considered MeeGo compliant? There is one caveat which people seem to forget - the joy is that we can rebuild Core and get a version for our processor because it is open source. But what about our applications? I mean, even open source will be difficult to deal with this problem. What will our MeeGo SDKs and community repositories/OBS target? Typically they will inherit the optflags from Core project configurations. You build for MeeGo X86, or MeeGo ARM. But is this MeeGo X86 (no processor related optimization flags) or MeeGo Atom? To deal with this in terms of compliance, I suggest we establish a MeeGo oompliance baseline for SDKs and community OBS to follow for applications. It doesn't have to be what Core is compiled for in MeeGo.com if we want to encourage MeeGo use on many different processors and devices. Your thoughts? Best regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
