Doug Turner wrote:
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
Keep in mind that you have to handle the case where the user of the libraries doesn't actually have write access to the directory that contains those libraries. This doesn't happen so often on win32 systems, but it definitely happens on unix systems. In this case, spawning regxpcom isn't going to get you anything, unless you can redirect the output to some local file, or even stdout and just read it in. :)
I'm not sure I like the spawn-regxpcom solution or not. I'd much rather just have a .dat file that's correct. I'm _still_ not sure why you need to re-register. This is something related to SVG?
--Chris
-- ------------ Christopher Blizzard http://www.mozilla.org ------------
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
