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


On Thu, Aug 18, 2011 at 10:34 PM, Olivier Hallot
<olivier.hallot@documentfoundation.org> wrote:
Hi
I am trying to build under windows 7 64Bits. I have installed Microsoft
Windows SDK, but autogen is not able to find it no matter the trials I made.

So can someone tell me what is the exact path to pass to
"--with-windows-sdk-home"?

The SDK is in 2 places:

C:\Program Files (x86)\Microsoft SDKs

C:\Program Files\Microsoft SDKs

Which one is the good one?

The SDK is usually automatically found through the oowintool utility.
In the cases where it is not found the problem is usually because the
tool finds the SDK installed by your compiler, which is very
incomplete and misses some of the required components. The safe bet is
to install the same Microsoft SDK version as the one incompletely
provided by your compiler (6.0A for Visual Studio 2008, if I remember
well)

The configure script looks for certain files inside those directories,
so I guess the problem is that does files don't exist (probably
because you did not install some required optional component):

Lib/libcp.lib
Include/adoint.h
Include/SqlUcode.h
Include/usp10.h
lib/user32.lib
bin/msiinfo.exe
bin/msidb.exe
bin/uuidgen.exe
bin/msitran.exe

Last but not least, it's also possible that the newest Microsoft SDK
has some changes that requires that we update our detection.

Hope that helps a bit :)

-- 
Jesús Corrius <jesus@softcatala.org>
Document Foundation founding member
Mobile: +34 661 11 38 26
Skype: jcorrius | Twitter: @jcorrius

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.