David Fraser wrote:
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)' .
Yes, a slightly odd output of AC_PATH_PROG(MSPDB_PATH, mspdb71.dll), the no basically says it didn't find it in path and then configure continues to look for it elsewhere. Be sure, if mspdb71.dll would not be found configure breaks with an error.
Without setting for csc path, configure stopped. With correct --with-csc-path, it passed with message, 'checking for csc.exe... no'
Same here
. 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)' .
Yes, see the build instructions. If NSIS is not installed/provided the nsis package of OOo is not build. But there is still the normal, unpacked installation set.
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.
See above. It would fail if midl.exe would be missing.
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.
That's what <http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#GeneratingtheBuildEnvironmentandBuildTools> says. The documentation and the output of configure should state this more clearly.
For now, I am going to stick with PATH variable method which gives me more comfortable output. :-)
Purely cosmetic, if you look at config_office/configure.in you see that you can ignore the slightly misleading output. It should read: checking for mspdb71.dll in PATH... no -------------------------^^^^^^^
I have also noticed that the configure output seems to be wrong, and the expected arguments to configure are strange without explanation...
I'm always happy to review patches. ;) Volker -- If you like my work consider: http://www.scytek.de/donations.html PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
signature.asc
Description: OpenPGP digital signature
