Bráulio Barros de Oliveira wrote:
> I had already tried setting QT_PLUGIN_PATH both on eclipse and on the shell
> and unfortunetely it didn't work.
> QApplication.addLibraryPath("/home/braulio/qtjambi-linux32-gpl-4.3.4_01/plugins");
This one is the correct to use.
> The abose function put just after QApplication.initialize(args) also didn't
> worked
> Also, I've restored the original sqldrivers directory, which contains the
> libqsqlite.so driver only.
> In both cases the list of available drivers is empty. (shouldn't it show at
> leeast the sqlite driver?)
Have you lost jpeg support as well? If you start the launcher and open
the image viewer, can you see jpegs?
> Another insteresting thing i've noticed is that the output of
> System.out.println(QLibraryInfo.location(QLibraryInfo.LibraryLocation.PluginsPath));
> is /home/qt/package-builder/qt-gpl/plugins. Shouldn't it be a relative path,
> as this is a static package (qtjambi-linux32-gpl-4.3.4_01.tar.gz)?
This is how qt binaries work, unfortunatly. The hardcoded paths in the
binary are created at compile time. You can replace them using a number
of deployment tricks, such as setting QT_PLUGIN_PATH, adding library
path or creating your own qt.conf file
(http://doc.trolltech.com/4.4/qt-conf.html). From Java these approaches
are less than ideal, which we recommend the JDBC approach. With 4.4's
improved deployment system most of the plugin nastyness is also handled.
-
Gunnar
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
