Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Frank Schoenheit, Oracle]

Hi Tor,

>> 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.
> 
> OK. So I guess it is recommended then indeed to not use the
> --disable-nss-module switch, even if one does use
> --disable-build-mozilla?

Yes. NSS is used for more than the Mozilla stuff, and the version in
module nss is more recent that what ships with the prebuilt SeaMonkey.

Ciao
Frank

-- 
ORACLE
Frank Schönheit | Software Engineer | frank.schoenh...@sun.com

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Tor Lillqvist]

> 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.

OK. So I guess it is recommended then indeed to not use the 
--disable-nss-module switch, even if one does use --disable-build-mozilla?

I guess our confusion here is caused by thinking that nss and nspr are just 
part of mozilla, and as one is using prebuilt mozilla, one shall not building 
the nss stuff included with OOo either.

--tml



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Frank Schönheit]

>>> 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: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Ruediger Timm]

On 07/01/10 14:18, Tor Lillqvist wrote:

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.

--tml



Those two libs AFAIK originate from module nss.

Rüdiger

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Stephan Bergmann]

On 07/01/10 14:38, Frank Schönheit wrote:

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.


Phh. Indeed: In the RC2 which I have here (and which should be identical
to the final release), nspr4.dll is linked against msvcr90.dll.

The strange thing is: In the respective WNTMSCIruntime.zip, which is
committed to the sun-internal repository (in a module called
moz_prebuild), and used during the build, the nspr4.dll is linked
against msvcr80.dll.

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.

In any way, that's a question for our release engineering, I'd say.


Maybe caused by RE not doing full builds?

-Stephan

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Frank Schönheit]

Hi Tor,

>> 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.

Phh. Indeed: In the RC2 which I have here (and which should be identical
to the final release), nspr4.dll is linked against msvcr90.dll.

The strange thing is: In the respective WNTMSCIruntime.zip, which is
committed to the sun-internal repository (in a module called
moz_prebuild), and used during the build, the nspr4.dll is linked
against msvcr80.dll.

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.

In any way, that's a question for our release engineering, I'd say.

Ciao
Frank

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Tor Lillqvist]

> 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.

--tml



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Frank Schoenheit, Sun Microsystems Germany]

Hi *,

>> Especially, the DLLs on the website use msvcr80.dll, while of the
>> ones in the installer, some use msvcr90.dll and others (ones not
>> actually used  by OOo, perhaps?) use msvcr80.dll.

Actually, *all* of the Mozilla libraries should be linked against
msvcr80.dll, while all of the "pure" OOo libs should be linked against
msvcr90.dll.

The reason is that Mozilla/SeaMonkey is built with an older compiler
(.NET 2005, IIRC), while OOo itself is built with a newer one (.NET 2008).

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?

> Most probably an oversight.  The prebuilts are checked into a 
> Hamburg-internal repository, and the accompanying README says "...and 
> upload to ", but this 
> has probably been forgotten the last time they were changed (at 
> , Frank?).

No, I updated the prebuilts at the website when I fixed this bug:
http://tools.openoffice.org/source/browse/tools/www/moz_prebuild/OOo3.2

Ciao
Frank

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Frank Schönheit]

Hi Christian,


>> Actually generating those prebuilts is something of a black art (esp. on
>> Windows), so it might be hard to trace back why the differences wrt msvcr
>> versions exist.
> 
> Cannot speak for windows build, but "dmake zip" in moz after compiling
> moz will create those zips.
> I'd not call that "black art" :-)

That's new then ... last time I had to bother with building SeaMonkey,
it could be built with .NET 2005, but /not/ with .NET 2008, while OOo
could be built with .NET 2008, but /not/ with .NET 2005.

So, effectively, I always needed one build environment for building
SeaMonkey and creating the prebuilts, and one for building OOo, using
those prebuilts.

The black art part was setting up the first of those two build
environments ...

Ciao
Frank

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Stephan Bergmann]

On Jun 30, 2010, at 7:54 PM, Christian Lohmaier wrote:
> On Wed, Jun 30, 2010 at 5:24 PM, Stephan Bergmann
>  wrote:
>> On 06/30/10 17:05, Tor Lillqvist wrote:
>> 
>> Actually generating those prebuilts is something of a black art (esp. on
>> Windows), so it might be hard to trace back why the differences wrt msvcr
>> versions exist.
> 
> Cannot speak for windows build, but "dmake zip" in moz after compiling
> moz will create those zips.
> I'd not call that "black art" :-)

The black art is how to set up a (Hamburg setsolar based) build environment so 
that the prerequisites for building moz are available (which is not normally 
built in the Hamburg setsolar environment, as the prebuilts are used instead) 
and the resulting binaries match the OOo baseline for the respective platform.

-Stephan

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Christian Lohmaier]

Hi Stephan, *,

On Wed, Jun 30, 2010 at 5:24 PM, Stephan Bergmann
 wrote:
> On 06/30/10 17:05, Tor Lillqvist wrote:
>
> Actually generating those prebuilts is something of a black art (esp. on
> Windows), so it might be hard to trace back why the differences wrt msvcr
> versions exist.

Cannot speak for windows build, but "dmake zip" in moz after compiling
moz will create those zips.
I'd not call that "black art" :-)

ciao
Christian

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Stephan Bergmann]

On 06/30/10 17:05, Tor Lillqvist wrote:

I noticed that the prebuilt Mozilla DLLs in the 
http://tools.openoffice.org/moz_prebuild/OOo3.2/WNTMSCIruntime.zip file (linked 
from the http://tools.openoffice.org/moz_prebuild/OOo3.2/ page) differ from the 
ones included with the OOo_3.2.1_Win_x86_install_en-US.exe installer.

Especially, the DLLs on the website use msvcr80.dll, while of the ones in the 
installer, some use msvcr90.dll and others (ones not actually used  by OOo, 
perhaps?) use msvcr80.dll. Is this intentional? Is this set of 
msvcr90.dll-using Mozilla DLLs (and then corresponding headers and import 
library) available prebuilt in similar zip files outside Sun? Is this 
intentional product differentiation or just an oversight?


Most probably an oversight.  The prebuilts are checked into a 
Hamburg-internal repository, and the accompanying README says "...and 
upload to ", but this 
has probably been forgotten the last time they were changed (at 
, Frank?).


Actually generating those prebuilts is something of a black art (esp. on 
Windows), so it might be hard to trace back why the differences wrt 
msvcr versions exist.


-Stephan

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

[dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer

[Tor Lillqvist]

I noticed that the prebuilt Mozilla DLLs in the 
http://tools.openoffice.org/moz_prebuild/OOo3.2/WNTMSCIruntime.zip file (linked 
from the http://tools.openoffice.org/moz_prebuild/OOo3.2/ page) differ from the 
ones included with the OOo_3.2.1_Win_x86_install_en-US.exe installer.

Especially, the DLLs on the website use msvcr80.dll, while of the ones in the 
installer, some use msvcr90.dll and others (ones not actually used  by OOo, 
perhaps?) use msvcr80.dll. Is this intentional? Is this set of 
msvcr90.dll-using Mozilla DLLs (and then corresponding headers and import 
library) available prebuilt in similar zip files outside Sun? Is this 
intentional product differentiation or just an oversight?

Linking to msvcr90.dll is obviously preferred, as that is what OOo itself uses. 
Using Mozilla DLLs that link to msvcr80.dll means one has to include that 
runtime, too, in one's installer, doesn't it?

--tml



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org