On Tuesday, 26 de October de 2010 16:48:52 [email protected] wrote: > As I said in earlier thread, this is my fault. I should have undesrtood the > signifigance and start that work early enough in MeeGo so we would have > had change to get it into 1.1 already. My only defence is that this is > pretty new stuff, and for the record, I am not ARM expert at all .. > > This important e.g. for Qt & Opengles, and we have that all over the place, > even increasingly in the future. I don't see any other possibility that > breaking the ABI now when we acn manage it, and also speak about that > openly. > > Sotimes we make mistakes, and then we need to correct them.
I'm not looking at assigning blame. And from what I hear, even if you had
thought of this earlier, we couldn't switch to hardfp now anyway because there
are certain software that won't work with it. We need to fix them first.
(We just benefit from Harmattan fixing them, since Harmattan has switched to
hardfp)
Also, the report showing that hardfp was a problem only appeared on my desk
about a month ago.
--
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
