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?
If LD_LIBRARY_PATH is set like so: path/to/gre:path/to/application:(and optionally)path/to/application/plugins
Dependent lib loading happens correctly and automatically, and you don't need to manually load any dependent libs.
You could set LD_LIBRARY_PATH
1) in a shell script that finds the GRE (you avoid ever manually loading dependent libs)
2) by having the application setup the environment and call "regxpcom" as a sub-process (you avoid manually loading dependent libs at autoregistration, but you still have to manually load them
> 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
Heh, the vagaries of soloading ;) but you're right, we can't count on this behavior since we don't know when the GRE is being initialized and what's already happened.
When I talked with blizzard, I presented my major issue that users would be told to delete compreg.dat (a standard support recommendation), and wouldn't be able to rebuild it (on *nix only), because they wouldn't know which GRE is the "correct" one.
--BDS
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
