Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


2013/11/21 Michael Stahl <mstahl@redhat.com>

On 21/11/13 12:00, Dali wrote:
Hi everyone,

I had a successful build of LibreOffice-4.0.6. Here is my conf:
- Build Environment: Windows 7 (64 bits)
- Microsoft Visual Studio version: 2012 update 4
-Autogen.lastrun:

[...]

--with-windows-sdk-home=C:\Program Files\Microsoft SDKs\Windows\v7.1

I can install the msi result on Windows 7 and it works fine. I can also
install it successfully on *Windows XP* but i have this message when i
try
to run LibreOffice:
-"..*soffice.exe is not a valid Win32 program*" => It doesn't work

I really need and appreciate your help to fix this problem on Windows XP
!!!!

on the libreoffice-4-1 and master branches you can fix this with the
configure switch --with-windows-sdk=7.0A ... but that does not work on
libreoffice-4-0 branch; there is a --with-windows-sdk-home switch.... oh
you're already using that one.

sorry, no idea why that doesn't work - MSVC2012 support was still
experimental in those days anyway.



As usual, our MSDN friends have all the information you need here:

https://blogs.msdn.com/b/vcblog/archive/2012/10/08/10357555.aspx?Redirected=true

We don't officially support Windows 2012 for the 4.0 branch, so please
don't distribute any 4.0.x release built with this compiler version (as,
even if it compiles, other unexpected problems may appear). But feel free
to play with it for development purposes.

-- 
Jesús Corrius <jesus@softcatala.org>

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.