Em Quinta-feira 08 Julho 2010, às 18:21:16, Carsten Munk escreveu: > Would an unofficial build of MeeGo totally matching Core sources, > built for I486 be considered MeeGo compliant?
I sure hope so. I mean, how can "rebuilding" be non-compliant?
> But what about our applications? I mean, even open source will be
> difficult to deal with this problem.
What do you mean?
> 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?
Changing compiler flags should be quite easy. And it should depend on the
device profile you're targeting, not your host. If I'm building for an Atom
device, I want all optimisations for Atom. If I've got a MIPS device
connected, I'd like to use the MIPS cross-compiler and get the best
optimisations for it.
And if I'm building for simulation on my host, I want it to run on my host :-)
Once I publish my Open Source application, it's up to the OBS to compile it
properly.
The worry I have is with the non-OSS apps that will be delivered.
> 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.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
