Ari Heitner wrote:

> And if that's the approach, the mozilla shared objects need to have
> appropriately versioned names, to allow multiple installs (even if you put
> mozilla in separate dirs by version, you need a way to let the linker link
> mozilla-dependent programs to the right libraries).

Note that it isn't the linker that gets libraries in the components
directory, it's XPCOM itself, using dlopen (or whatever the platform
uses, through NSPR).

In fact, that is one amusing detail with XPCOM, the name of the library
doesn't matter at all! It will survey all the libraries at
autoregistration time and will get components from whatever module
(library) they are in...

> In windows ... I don't know a good way of doing this in windows :)

You do it just like in Unix, as Microsoft itself is doing with MFC
(MFC30.DLL, MFC40.DLL, MFC42.DLL, etc) and the Visual Basic runtime DLLs
(VBRUN300.DLL, etc).

-- 
"Unix is the worst operating system; except for all others."
 -- Berry Kercheval



Reply via email to