>>> So if you say that in an OOo installed from a downloaded installer, >>> there are *Mozilla* libs (*not* OOo libs!) which are linked against >>> msvcr90.dll, I'd b somewhat surprised. Do you have an example? >> Sure. For instance nspr4.dll and nss3.dll in an OOo installed from >> OOo_3.2.1_Win_x86_install_en-US.exe downloaded on June 25. > ... > Conclusion: The files which finally appear in the install don't > originate from the location they're expected to. Or I am simply not > up-to-date - perhaps moz_prebuild is not the expected source of those > files anymore.
Heureka! Both files you mentioned indeed do not come from the Mozilla prebuilts, but from the nss module. Nowadays, either SeaMonkey is built from scratch, or the prebuilts are used. In both cases, you get DLLs linked against msvcr80.dll. However, in module nss, the NSS libs are built, too, in the .NET 2008 environment, means they're linked against msvcr90.dll. This is (should be) completely transparent, i.e. if you download the prebuilts used from tools.openoffice.org, and use them in your build, but also build the nss module (there's a configure switch to disable it, IIRC), then the libs from the latter replace the libs from the former. So, in an ordinary OOo build, you should also get a nspr4.dll linked against msvcr90.dll. So, finally, http://www.quotationspage.com/quote/1114.html wasn't that appropriate over there at ooo-build? Ciao Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
