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 <div class="gmail_quote">2011/8/19 Michael Meeks <<a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"> On Thu, 2011-08-18 at 22:58 +0200, Jesús Corrius wrote: > The SDK is usually automatically found through the oowintool utility. </div> 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. -- <a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a> <><, Pseudo Engineer, itinerant idiot </blockquote></div> -- Olivier Hallot Founder and Steering Commitee Member The Document Foundation