Re: --with-xxxx-path parameters does not work for configure script on Windows
David Fraser <[email protected]>
| Newsgroups | gmane.comp.openoffice.devel.tools |
|---|---|
| Message-ID | <[email protected]> |
Jeongkyu Kim wrote: >On 9/6/05, Volker Quetschke <[email protected]> wrote: > > >>Hi Jeongkyu, >> >> >> >>>For building OO.o 2.0 on Windows, I tried to set following parameters >>>but the paths don't count in configure script (I tried both long >>>format and 8.3 format). >>> >>>--with-mspdb-path >>>--with-midl-path >>>--with-csc-path >>>--with-nsis-path >>> >>>Is this my own problem or known issue? >>> >>> >>No, works just fine. If you tell us what you did, we could tell you >>what to change. >> >> >> > >This might be only for me but I was confused by configure output. > >Without setting for mspdb path, configure stopped. With correct >--with-mspdb-path, it passed with message, >'checking the Microsoft C/C++ Compiler... checking for mspdb71.dll... no >found (/cygdrive/c/PROGRA~1/MICROS~2.NET/Vc7/bin/cl.exe)' >. >Without setting for csc path, configure stopped. With correct >--with-csc-path, it passed with message, >'checking for csc.exe... no' >. >Without setting for nsis path, there was a warning at the end of >output. With correct --with-nsis-path, it passed with message, >'checking for NSIS... checking for nsis.exe... no >found (/cygdrive/c/PROGRA~1/NSIS)' >. >However, configure did not stopped without midl setting. And I tried both > --with-midl-path="/cygdrive/c/Program Files/Microsoft Visual Studio >.NET 2003/Common7/Tools/bin" and > --with-midl-path="/cygdrive/c/Program Files/Microsoft Visual Studio >.NET 2003/Common7/Tools" >but still I got a message, 'checking for midl.exe... no'. Thus I could >not confirm midl path was correctly set. > >And --with-cl-home was little bit tricky because I had to set >"/cygdrive/c/Program Files/Microsoft Visual Studio .NET 2003/Vc7" >instead of "/cygdrive/c/Program Files/Microsoft Visual Studio .NET >2003/Vc7/bin" which has cl.exe. > >For now, I am going to stick with PATH variable method which gives me >more comfortable output. :-) > > I have also noticed that the configure output seems to be wrong, and the expected arguments to configure are strange without explanation... David