Re: [Libreoffice] Newbie question: Windows SDK exact path
I build LO on Windows Server 2008R2 (i.e. the server version of Windows 7, 64-bit). I have the Windows SDK 7.0 installed in its default location(s), i.e. in C:\Program Files\Microsoft SDKs\Windows\v7.0 *and* C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A , with some overlap, partly same files in both locations. (Yeah, seems a bit weird to me, too, but as far as I can recall it is not myself who have done any weird choice here.) Anyway, from the config.log I see that it is the first one that is found and that gets used. If I run ./oowintool --windows-sdk-home it outputs /cygdrive/C/Program Files/Microsoft SDKs/Windows/v7.0 . --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
On Mon, 2011-08-22 at 02:11 -0600, Tor Lillqvist wrote: I build LO on Windows Server 2008R2 (i.e. the server version of Windows 7, 64-bit). I have the Windows SDK 7.0 installed in its default location(s), i.e. in C:\Program Files\Microsoft SDKs\Windows\v7.0 *and* C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A , with some overlap, partly same files in both locations. (Yeah, seems a bit weird to me, too, but as far as I can recall it is not myself who have done any weird choice here.) I had difficulties on a fresh install of all the recommended things. Attached was my hack-around fix for the problem I had, which might be the same fundamental problem. C. diff --git a/configure.in b/configure.in index 536ca8b..fd23669 100755 --- a/configure.in +++ b/configure.in @@ -6341,6 +6341,16 @@ if test $_os = WINNT; then if test -n $WINDOWS_SDK_HOME; then WINDOWS_SDK_HOME=`cygpath -d $WINDOWS_SDK_HOME` WINDOWS_SDK_HOME=`cygpath -u $WINDOWS_SDK_HOME` + +#If this sdk is incomplete, lets see if the one +#recommended to be installed is available +if test ! -x $WINDOWS_SDK_HOME/bin/msiinfo.exe; then +WINDOWS_SDK7_HOME=`cat /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft SDKs/Windows/v7.1/InstallationFolder 2 /dev/null | tr '\000' '\n' | head -n 1` +if test -n $WINDOWS_SDK7_HOME; then +WINDOWS_SDK_HOME=`cygpath -d $WINDOWS_SDK7_HOME` +WINDOWS_SDK_HOME=`cygpath -u $WINDOWS_SDK_HOME` +fi +fi fi else WINDOWS_SDK_HOME=`cygpath -u $with_windows_sdk_home` @@ -6385,14 +6395,15 @@ the Windows SDK are installed.]) fi fi + if test -z $WINDOWS_SDK_HOME; then AC_MSG_RESULT([no, hoping the necessary headers and libraries will be found anyway]) +elif echo $WINDOWS_SDK_HOME | grep v7 /dev/null 2/dev/null; then +AC_MSG_RESULT([found Windows SDK 7 ($WINDOWS_SDK_HOME)]) elif echo $WINDOWS_SDK_HOME | grep v6.1 /dev/null 2/dev/null; then AC_MSG_RESULT([found Windows SDK 6.1 ($WINDOWS_SDK_HOME)]) elif echo $WINDOWS_SDK_HOME | grep v6.0 /dev/null 2/dev/null; then AC_MSG_RESULT([found Windows SDK 6.0 ($WINDOWS_SDK_HOME)]) -elif echo $WINDOWS_SDK_HOME | grep v7 /dev/null 2/dev/null; then -AC_MSG_RESULT([found Windows SDK 7 ($WINDOWS_SDK_HOME)]) else AC_MSG_ERROR([Found legacy Windows Platform SDK ($WINDOWS_SDK_HOME)]) fi ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
Attached was my hack-around fix for the problem I had, which might be the same fundamental problem. Hmm, I know you say it's just a hack-around, but in general, I am not sure I like the idea of doing similar stuff as oowintool does (i.e. read the Registry through its Cygwin /proc/registry pathnames) in configure.in. (Yeah, I see that we already do that in one place...) I wonder if we should just move the oowintool code into configure.in? Sure, oowintool is Perl and configure.in is shell, but oowintool isn't that extremely perlish Perl, it would be relatively simple to implement its logic in shell code instead. That would keep all business logic related to compiler and SDK selection in one place. If we want to get fancy, one could even write a library of Autoconf macros for this;) An Easy Hack? --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
On Mon, 2011-08-22 at 03:46 -0600, Tor Lillqvist wrote: I wonder if we should just move the oowintool code into configure.in? Sure, oowintool is Perl and configure.in is shell, but oowintool isn't that extremely perlish Perl, it would be relatively simple to implement its logic in shell code instead. Cue language war ;-) personally I'd hate that, and having the tool standalone perhaps helps some quick debugging without re-autogenning etc. And of course truly-system-independent-non-bash shell is susbtantially uglier than perl but ... win32 is your world of course :-) ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
On Thu, 2011-08-18 at 22:58 +0200, Jesús Corrius wrote: The SDK is usually automatically found through the oowintool utility. And of course improvements to oowintool much appreciated - for a start we should put our license header on it I guess - it was not a Sun / Oracle tool. ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
Thanks guys I ran oowintool and it gave me (in cygwin), (Windows7 64 bits under a VirtualBox 4.1 VM). Olivier@Olivier-ntbk ~/libo $ ./oowintool --windows-sdk-home /cygdrive/C/Program Files/Microsoft SDKs/Windows/v6.0A Then I peeked at this directory: Olivier@Olivier-ntbk ~/libo $ ls -al /cygdrive/C/Program\ Files/Microsoft\ SDKs/Windows/v6.0A/ total 456 drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 14:48 . drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 15:15 .. drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 14:48 Include drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 14:48 Lib drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 14:48 bin but, but, but... I get this in autogen.sh: checking for Windows SDK... configure: error: Some (all) files of the Windows Installer SDK are missing, please install. There is another SDK in (note the x86): Olivier@Olivier-ntbk ~/libo $ ls -al /cygdrive/C/Program\ Files\ \(x86\)/Microsoft\ SDKs/Windows/ total 0 drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 15:09 . drwx--+ 1 SYSTEM SISTEMA 0 Aug 4 22:49 .. drwx--+ 1 SYSTEM SISTEMA 0 Aug 17 15:09 v6.0A drwx--+ 1 SYSTEM SISTEMA 0 Aug 4 22:50 v7.0A I am puzzled! Can Libo be built in a 64bit OS? Should I move to W7 or XP 32 bits? Thanks again Olivier 2011/8/19 Michael Meeks michael.me...@novell.com On Thu, 2011-08-18 at 22:58 +0200, Jesús Corrius wrote: The SDK is usually automatically found through the oowintool utility. And of course improvements to oowintool much appreciated - for a start we should put our license header on it I guess - it was not a Sun / Oracle tool. ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot -- Olivier Hallot Founder and Steering Commitee Member The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Newbie question: Windows SDK exact path
On Thu, Aug 18, 2011 at 10:34 PM, Olivier Hallot olivier.hal...@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 je...@softcatala.org Document Foundation founding member Mobile: +34 661 11 38 26 Skype: jcorrius | Twitter: @jcorrius ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
