> 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.
Communication should come to the rescue. These sentences are extracted from http://labs.trolltech.com/blogs/2010/05/06/qt-47-scope-change-regarding-qt-multimedia/ : > Today's beta packages still include a subset of the Qt Multimedia > functionality, but we will remove this code from Qt before the final release > of Qt 4.7.0. Not to fear however, this Multimedia API is part of the new Qt > APIs for mobile development package, released as Qt Solutions last week. > Second, the same use cases that are now in the Beta (plus more) are still > going to be available, with API and binary compatibility, from the Qt > Solutions release, and with roughly the same schedule. I see API and ABI promises here (something like Qt WebKit does). Could someone clarify Qt Multimedia/Kit situation ? _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
