Erwin Mueller wrote: > Thank you. So I could use LD_LIBRARY_PATH to point to /usr/lib64 or /usr/lib > and if there are no compatible libraries are found then the one in the jar > archive are used? > > Just tested it on my system and it appears to work. I put two libraries > paths, > one is /usr/lib64 and the other one is $JAMBI/lib. The first one will be > searched first and then the latter. >
No, we can't detect whether the system library is compatible, so you will have to make sure of this on your own. You need to *manually build* Qt Jambi from a source package against the Qt version which is installed on the system to which you are deploying. This is how binary deployment on Linux is typically done. If you deploy the Qt Jambi binary package against the system libraries, you are probably going to see crashes and memory corruptions down the line if not right away, because the configuration flags used when building the Qt Jambi binary package is incompatible with the configuration flags used when building KDE. If you do this, you *should not* use Qt Jambi's method of deploying libraries in .jar-files. Only use the .jar-file deployment if you are bundling every library you need in the .jar-file. The LD_LIBRARY_PATH deployment is Java's default way of resolving libraries, and is *an alternative* to using Qt Jambi's custom .jar-file deployment. -- Eskil _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
