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


Hi all,

Lubos Lunak schrieb:
On Monday 26 of March 2012, Kohei Yoshida wrote:
On Mon, Mar 26, 2012 at 5:14 PM, Regina Henschel

<rb.henschel@t-online.de>  wrote:
I have tried also with
--with-windows-sdk-home="/cygdrive/c/Programme/Microsoft
SDKs/Windows/v6.0A"

I believe that configure option has been renamed to
--with-dotnet-framework-home.  E.g. I have

     --with-dotnet-framework-home="/cygdrive/c/Program Files/Microsoft
SDKs/Windows/v7.0A"

in my configure option.

No, that does not solve the problem, neither with
--with-dotnet-framework-home alone nor in combination with
--with-windows-sdk-home

Hmm..  Anyone else have any ideas?

  I think one thing that has changed relatively recently is that the SDK must
be registered as default with Visual Studio (in the menu: Microsoft Windows
SDK 7.1 ->  Visual Studio Registration ->  Windows SDK Configuration Tool).

  You can also have a look at configure.in to see what the check actually looks
for.


I have examined configure.in and found this:
The automatic detection results in
$WINDOWS_SDK_HOME = /cygdrive/c/Programme/Microsoft SDKs/Windows/v6.0A
There configure is looking for the files
$WINDOWS_SDK_HOME/bin/msiinfo.exe
$WINDOWS_SDK_HOME/bin/msidb.exe
$WINDOWS_SDK_HOME/bin/msitran.exe
$WINDOWS_SDK_HOME/bin/uuidgen.exe

And indeed these files are not there. But I have found these files in
C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Bin
and in
C:\Programme\Microsoft SDKs\Windows\v6.1\Bin

So which are the correct ones to use?

Kind regards
Regina



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.