I'm not sure about the question, but right now LD_LIBRARY_PATH is set in run-mozilla.sh to include the application directory... is this what you're asking?
You still have to ship some kind of file that includes this LD_LIBRARY_PATH. What does it matter if it is in the compreg.dat (generated at build/release time) or in a .sh file?
right. On *nix it's not honored when loading SOs in the current process, only child processes.That is not completely correct. On some linux versions, if the the application has not explicitly called dl_open, and you set LD_LIBRARY_PATH, the next dl_open call will honor the newly set ld path. At least this is what i remember. And yes, this constraint doesn't work for some/most embedders.
Doug Turner
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
