On Sep 17, 2010, at 12:38 AM, <[email protected]>
<[email protected]> wrote:
> Changing QT_PLUGIN_PATH to include the plugins directory (i.e.
> /opt/qt4-maemo5/plugins) will probably get you up and running.
>
You're right. Changing my plugin path to the following seems to help. I
formerly had it to /opt/qt4-maemo5 because that worked fine for the sensors
examples.
I still have the following issue though:
QMediaPluginLoader: Failed to load plugin:
"/opt/qt4-maemo5/plugins/mediaservice/libqtmedia_v4lengine.so" "The plugin
'/opt/qt4-maemo5/plugins/mediaservice/libqtmedia_v4lengine.so' uses
incompatible Qt library. Expected build key "armv6 linux g++-4 full-config",
got "arm linux g++-4 full-config""
Why does my scratchbox produce a different build key? How would I change this?
> I'm guessing what's happened though is you have configured Qt and QtMobility
> without specifying an install prefix, so both are being installed to default
> locations instead of where you want them.
>
> If you do a new build of both with '-prefix <install path>' added to your
> configure arguments then make install should install everything to the
> correct location and there shouldn't be any need for environment variables to
> find plug-ins or libraries.
Correct. I didn't set an install prefix. They are getting installed into
qt-mobility/install instead and I am copying them manually. I will try to
build packages using:
dpkg-buildpackage -b -D -rfakeroot -us -uc
Let me know if there is a better / more simpler way.
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback