Hi Alex, On Fri, 2010-12-03 at 01:45 +0100, [email protected] wrote: > The relevant code is in src/global/qmobilitypluginsearch.h. The location > library includes this header for its plug-in logic: > > inline QStringList mobilityPlugins(const QString& plugintype) > > There are a couple of dir.exists() calls which might cause some paths to be > skipped. This is of particular importance if your plug-in is not in a > subdirectory called "plugins/geoservices". What's the absolute path of the > directory where your plug-in can be found?
you are right. If I move the 'geoservices' dir into the 'plugins' dir, it works. The problem was that I was expecting Qt Mobility plugins to work like ordinary Qt plugins. And if I deploy Qt plugins bundled with my application, I don't need the 'plugins' directory. Instead the directory where the application is started from directly contains the subfolders of 'plugins'. This is described here [1]. "" When the application is run, Qt will first treat the application's executable directory as the pluginsbase. For example if the application is in C:\Program Files\MyApp and has a style plugin, Qt will look in C: \Program Files\MyApp\styles "" I think it should work the same way in Qt Mobility. What do you think? Conny [1] http://doc.qt.nokia.com/4.7/deployment-plugins.html _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
