this means essentially copying much of the code in prlink.c ... are you sure that is wise?
-darin
Shared objects and dlls are for saving system ressources and for modularization. If you have to ship a certain set of libraries with every application it doesn't save ressources and the modularization is pointless too. The saving ressources aspect is only possible, when every application uses the same globally accessible library, and the GRE libraries are globally accessible only after you connected to it. But for connection it needs a subset of the functionality of nspr. So the most straightforward way to connect would be to statically link this subset to the xpcomglue you need staticaly linked anyway. And all this should be possible without writing or copying any C++ code. Just by justifying makefiles.
Ideally, all you need in the gecko SDK is one lib directory with one static xpcomglue in it, that contains all the objects it needs to connect, and maybe even merges with the embedstring library. Everything you don't need in your app the linker leaves out anyway. So I guess the SDK would be much more coder friendly if it would contain just
- one lib dir with the staic glue
- one include dir with all the headers of the interfaces GRE provides (no matter if frozen or not...it's not that hard to hunt down changed interfaces, and the interfaces in GRE are comparibly stable, regardless of their state)
- one bin dir with the idl tools and the needed dynamic libraries fro them, maybe the wintools as well
- documentation
So doing all this would ease development considerably, sparing a lot of searching in ftp.mozilla.org and www.mozilla.org and mozdev.org. All you need to embed or extend mozilla then is the sdk. And if you need more information, just get the sources. And you don't have to add a dozen lib and include dirs to the compile but only one, and you don't have to add a dozen bin dirs to your path, but only one, and you don't have to add a dozen environment variables. And you don't have to spare an hour every once in a while to build mozilla.
But well, it works for now as well. But speaking only of myself, I needed almost a week of web research an tool assembling, before I actually could write the first line of code to embed the GRE (I was only mozilla end user up to then).
But nonetheless, Mozilla is a great poject, and saves us all a lot of coding.
Jan
_______________________________________________ mozilla-embedding mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-embedding
