Hi Espen, QtMultimediaKit in Mobility has a different namespace so that it does not conflict with the low latency classes in QtMultimedia. They are source compatible. So rather than merging MultimediaKit code to Qt, just download Mobility and build MultimediaKit to create a library.
Regards, Min -----Original Message----- From: qt-mobility-feedback-boun...@trolltech.com [mailto:qt-mobility-feedback-boun...@trolltech.com] On Behalf Of ext Espen Riskedal Sent: Thursday, 9 December 2010 11:53 PM To: Luoma Antti Cc: qt-mobility-feedback@trolltech.com Subject: Re: [Qt-mobility-feedback] Clarifying questions around QtMultimedia On Thu, Dec 9, 2010 at 9:09 AM, Luoma Antti <antti.lu...@digia.com> wrote: > Hi, > > There is some documentation being made that take account on this. It is not > yet published. It's been a long time since any update, it would be great to hear whats cooking. >>1) Are the classes in Qt Mobility that are also present in Qt (like >>QAudioOutput) a _copy_ - or is it just simply relying on Qt, and if >>you include <QAudioOutput> from Mobility, it will actually include the >>.h from Qt? > > Development is now being done in QtMobility repositories. Originally those > classes where merged from Qt and > the latest code is now under QtMobility. OK, but does that mean for each Qt release you merge back the QAudioOutput classes from Mobility into Qt? > On Symbian system include will include headers from epoc32\include\ and there > should not be 2 set of same > headers under that directory tree. Well, one .h could just include the other .h , ie - it's the same header only a shallow redirect. Still a bit confused, but thanks for the update :) espen _______________________________________________ Qt-mobility-feedback mailing list Qt-mobility-feedback@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback _______________________________________________ Qt-mobility-feedback mailing list Qt-mobility-feedback@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
