Hi Kristján,

Kristján Bjarni Guðmundsson schrieb:
Hi.

I am trying to build OpenOffice on Windows XP using cygwin.
I am using the OOo-Dev_DEV300_m51 source archive.

I have set up everything according to:
http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_on_windows

There is a more recent description in
http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows
There are some problems with spaces, non default paths and case sensitivity. Please have a look.


But when I run configure:
./configure --disable-build-mozilla --disable-activex
--with-directx-home=/cygdrive/c/PROGRA~1/MI22C6~1

Everything goes ok until this:

can't find /cygdrive/C/Program Files/Microsoft Visual Studio
8/VC/../SDK/v2.0/Bin at ./oowintool line 283.
configure: error: oowintool failed to copy CRT

However this directory does exists. But why is it trying to copy CRT from
this directory? Shouldn't it be using one of the
msvcp directories in external? Can anybody see what I am doing wrong here?

Perhaps you can post your complete configure?

My configure on WinXP is
./configure \
 --with-directx-home=/cygdrive/c/Programme/dxsdk \
 --with-cl-home="/cygdrive/c/Programme/Microsoft Visual Studio 9.0/VC" \
 --disable-activex \
 --disable-build-mozilla \
 --disable-directx \
 --disable-epm \
 --disable-atl \
 --with-win32 \
 --with-frame-home="/cygdrive/c/Programme/Microsoft SDKs/Windows/v6.1" \
 --with-psdk-home="/cygdrive/c/Programme/Microsoft SDKs/Windows/v6.1" \
--with-midl-path="/cygdrive/c/Programme/Microsoft SDKs/Windows/v6.0A/Bin" \ --with-asm-home="/cygdrive/c/Programme/Microsoft Visual Studio 9.0/VC/Bin" \
 --with-jdk-home="/cygdrive/c/Programme/Java/jdk1.6.0_06" \
 --with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
 --with-ant-home=/apache-ant-1.7.0 \
 --with-use-shell=bash

But I'm no developer and so cannot really help you.

kind regards
Regina




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to