On 01.12.2010 13:58, Kristján Bjarni Guðmundsson wrote:
I am building DEV300_m94 on Windows with this configure:

./configure --with-lang="is" --with-vendor="OpenOffice.is"
--with-build-version="Build by OpenOffice.is" --disable-activex
--disable-directx --disable-atl --disable-build-mozilla --disable-nss-module
--without-junit --with-cl-home="/cygdrive/C/Program Files/Microsoft Visual
Studio 9.0/VC" --with-ant-home="/cygdrive/c/winapps/java/ant"
--with-frame-home="/cygdrive/C/Program Files/Microsoft SDKs/Windows/v6.1"
--with-psdk-home="/cygdrive/C/Program Files/MicrosoftSDKs/Windows/v6.1"
--with-midl-path="/cygdrive/C/Program Files/Microsoft SDKs/Windows/v6.1/Bin"
--with-asm-home="/cygdrive/C/Program Files/Microsoft Visual Studio
9.0/VC/Bin"
--with-jdk-home="/cygdrive/C/Winapps/java/jdk16"
--with-csc-path="/cygdrive/C/WINDOWS/Microsoft.NET/Framework/v3.5"

Looks fine.

It seems to me the the problem is that the generated install doesn't contain
the redistributable vcredist_x86.exe file. This seems to have been changed in
some release of the source code, since previous builds before worked. If
you install the vcredist_x86.exe then OpenOffice.org can be started. The
normal install from OpenOffice.org does however contain the vcredist_x86.exe 
file,
so this must be a difference in how the builds are created. Why is this?

Somewhere on the way to OOo3.2 we changed the way how the vcredist is packed. I'm not sure if it was the intent that there is no configure switch to allow packing with vcredist. The only reasons that come to my mind could be legal issues. Perhaps Martin (on CC) knows that better.

Regards,
Mathias

--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Oracle: http://blogs.sun.com/GullFOSS
Please don't reply to "[email protected]".
I use it for the OOo lists and only rarely read other mails sent to it.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to