Re: [dev] instsetoo_native: Assembly missing for Windows install
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 nospamfor...@gmx.de. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] instsetoo_native: Assembly missing for Windows install
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 There are no problems configuring and building the install. The problem is after installing the resulting install on Windows XP SP3. Starting for example Writer reports the following: C:\Program Files\OpenOffice.org 3\program\swriter.exe This application has failed to start because the application configuration is incorrect. Re-installing the application may fix this problem. In the event log this error is seen: Generate Activation Context failed for C:\Program Files\OpenOffice.org 3\Basis\program\shlxthdl\shlxthdl.dll. Reference error message: The operation completed successfully. Resolve Partial Assembly failed for Microsoft.VC90.CRT. Reference error message: The referenced assembly is not installed on your system. Dependent Assembly Microsoft.VC90.CRT could not be found and Last Error was The referenced assembly is not installed on your system. 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?
