Hi, > I'm building QtMobility (just multimedia) on Windows. I've using 1.0.2 > with Qt 4.6.2 but I've also tried the same test with 1.1.0-tp and Qt > 4.6.3. > > Everything builds OK and my release version runs fine. > > But for either the debug version, I get messages like this when it > tries to load the plugins: > > QMediaPluginLoader: Failed to load plugin: > "C:/QtMobility/plugins/mediaservice/dsengine.dll" "The plugin > 'C:/QtMobility/plugins/mediaservice/dsengine.dll' uses incompatible Qt > library. Expected build key "Windows msvc debug full-config", got > "Windows msvc release full-config"" > > Somehow, it seems, the path for the plug-in is being hard coded into > the DLLs. But what's strange is that the hard coded path is not used > all of the time. > > If I do not put the 'mediaservice' plug-in directory in the same > directory as my .exe, then it simply says the media service cannot be > found (as a log message when I run the .exe). This is as expected. > > On the other hand, if I put the media service plug-in directory into > the same folder, it finds the plug-ins, but then seems to do another > check that results in the error message above. > > Finally, if I put the debug versions of the plug-ins (see below) into > C:/QtMobility/plugins/mediaservice and remove the release versions, > then things work OK for the debug version and I have the symmetric > problem with the release version. > > On debug plug-ins: When I do this: > > configure -modules multimedia > nmake > nmake install > > It will build the whole project in debug and release form, except for > the plug-ins which only get built in release (not debug) form. > > To build the plug-ins in debug form, I do: > > nmake debug > > Bottom line... what am I missing about the installation procedure? > What is the proper technique to build the plug-ins? What key magic > ingredient am I missing here?
I've tried both 1.0 and 1.1 HEAD against Qt 4.7 and both the release and debug plug-ins were installed to plugins/mediaservice in each case. This looks to be fix here: http://qt.gitorious.org/qt-mobility/qt-mobility/commit/e5cb87e2886bd3dd3b88cebf81de8c3f3875a628 Building the plug-ins in debug form and copying them directly should work as well. The debug dll's have d prefix so they can live side by side with the release plug-ins just fine. There will still be warnings because the loader will try all dlls and simply reject those that don't match the build configuration of the application and output a warning in the process, provided it does load the plug-in for the correct configuration you can ignore these. Andrew _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
