Hi All!

Few month ago I asked about possibility to create some "Jambi Runtime"
to make it possible to install single Jambi distribution for all
platform software. Now I have working solution, and want to make my
small contribution. Attached diff makes NativeLibraryManager to search
"JAMBI_LIBRARY_PATH" first, than standard Jambi initialization
process.

I took 
http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-installation.html#load-issues
as base for following points:

Small intro why I did it like this:
1. java -D args are great, but you have to specify it for each
application, need to create own launch scripts. While I wanted to make
it possible to run ANY Jambi application without that path magic, just
by running it's jar.
2. Two big reasons against classpath: 1) I have some kind of paranoia
and I don't want to overload my Classpath with additional classes. 2)
It's just didn't worked on my system.
3. Subdirectory bin or lib just not a bit better than distributing
with platform-specific JAR.
4. LD_LIBRARY_PATH or PATH just not suitable. I have Perforce and
QtSdk already in PATH, all of them are using different versions of Qt,
and I am afraid that modification of PATH can hurt other Qt-based
software.

Next step: I'll create small installator for Windows with NSIS that
will install required dlls and will setup JAMBI_LIBRARY_PATH variable.
Later I'll try to modify SUSE-specific .spec file of QtJambi to setup
the same variable.

Hope you'll like it and something similar will be included in
qtjambi-4.5.0_02.jar.

Attachment: NativeLibraryManager2.diff
Description: Binary data

_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest

Reply via email to