Howard Chu wrote: > Peter Ekberg wrote:
[snip] > >>>I configure the libtoolized project with > >>> > >>>.../configure CC="cl -MD" LDFLAGS=-L/msvc/lib > >>> > >>>Where MSYS has a mount so that /msvc points to the MSVC folder > >>>(typically "C:\Program Files\Microsoft Visual Studio\VC98" > >>>or something similar) > >> > >>Yeah, it might be necessary to work around all the `white > >>space in path' issues as well... > > Yes. But my VCVARS32.BAT file uses DOS-compatible paths (E.g. > C:\PROGRA~1\MICROSO~4) so there's no whitespace in my paths. > (And I call > that batch file from the MSYS batch file so that MSVC is setup in my > MSYS environment. Likewise for Cygwin.) Yes, mine does to. But when I installed Visual Studio, I was asked if I wanted to add these vars to my environment permanently, which I wanted, and it was not the spaceless versions that was added. And the VCVARS32.BAT file simply adds the needed directories, so the long paths will still be there even if I do run the BAT-file. If I want to get rid of the paths with spaces, I have to edit the environment manually from the control panel. So, if this is to be handled seamlessly, spaces in $LIB has to be handled, as they are so bleeding common. Perhaps it doesn't need to be seemless though? Howard, do you currently use MSVC with libtool? Cheers, Peter
