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.
The reason for dependent libs is to break that requirement. LD_LIBRARY_PATH would just have to be set to path/to/application.
You could set LD_LIBRARY_PATH
1) in a shell script that finds the GRE (you avoid ever manually loading dependent libs)
This isn't going to work very cleanly for folks that want to embed gecko.
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
This could be done. Where do you propose to store the library path?
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.
We can rename this file in future versions.
Doug Turner
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
