On Sunday, 31 de October de 2010 20:51:21 alex.blas...@nokia.com wrote: > Not every Qt API consists of plug-ins as their backend. In general, that's > only done if it is likely that the same device image should/could be > extended/changed during the same device's lifetime (e.g. add more codecs, > use a different maps provider etc). Otherwise a plug-in solution is too > expensive for multiple reasons. The same applies to things like connman, > ofono or other types of platform API's. Most Qt libraries with ties to > those platform API's do not have a plug-in mechanism for their backends.
It's perfectly ok that some device vendors recompile certain libraries for
better performance or, like in this case, linking to different libraries.
However, they'll need to make their changes available to the community
(QtMobility is LGPL).
Also note that "if it is likely that the same device image should/could be
extended/changed during the same device's lifetime" is actually incorrect. The
guiding principle is not about one device's image, but the MeeGo release image
(which spans all devices).
Recompilations by vendors are the exception, not the rule, and they usually
will rebuild only a couple of packages.
--
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 MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
