Em Quinta-feira 17. Junho 2010, às 08.36.14, [email protected] escreveu: > > For MeeGo 1.1 I'm hoping we can have Qt 4.7.0 final. The dates (still) > > match, since we plan on releasing in August, before the freeze of core > > components for MeeGo. QtWebKit should be built from Qt, definitely > > Why ? afaik, Qt WebKit is planned to be released before Qt 4.7.0 final. > > > but it will probably be upgraded by an external package later on. > > Whether MeeGo will upgrade to QtWebKit 2.1 or stick to 2.0, I don't know. > > It will probably not upgrade until MeeGo 1.2. > > I fail to see why it can't be an external package for MeeGo 1.1 as the > release plan should match.
I don't know when the QtWebKit 2.0 package (the tarball) will land. If we
release the tarball at the same time, then you can choose which one to build.
But if we don't, then at least QtWebKit 2.0 will be included in Qt 4.7.0, so
that situation is clear there.
> > As for multimedia, it's required by Mobility. You can't compile it out.
>
> No, Multimedia isn't required by Mobility:
> - you can build Qt Mobility against Qt built with -no-multimedia
> The MultimediaKit module of Qt Mobility will be built in this case
> - you can build Qt Mobility against Qt built with -multimedia
> The MultimediaKit module of Qt Mobility will not be built in this case but
> you will have Multimedia module from Qt.
Well, either way, a FULL build of Qt will be provided, with all features.
QtMultimedia is part of Qt 4.6, so it will have to stay there until 5.0.
MultimediaKit from Mobility doesn't carry the same soname, even if it carries
copies of the same classes.
--
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
