Re: Support for VC++ toolchain (was Re: Absolute paths generated by libtool.)

[Benoit Sigoure]

Quoting Howard Chu <address@hidden>:
> Benoit Sigoure wrote:
> > Quoting Benoit Sigoure <address@hidden>:
> > > [SNIP, see http://lists.gnu.org/archive/html/libtool/2006-11/msg00018.html]
> >
> > Hello folks,
> > I think I finally succeeded: I can now build any UNIX program as long as its
> > code is portable on Windows with both mingw-gcc toolchain and MS VC++.
>
> Wow, what a lot of effort, when you could have simply installed MSYS 
> and the cccl shell script. I guess you would still need to intercept 
> DOS-style commands like del and xcopy, but the MSYS shell takes care 
> of command line arguments and paths, and cccl takes care of 
> translating Unix cc options to switches that MSVC understands. With 
> these I can use an unmodified libtool script to build most autoconf'd 
> packages on Windows.

No sorry, this was necessary. MSYS isn't enough, and using it wouldn't have
enabled me to do what I do now. The shell still removes unecessary backslashes
and MSYS can't automagically handles things such as:
gcc -I/home/build/... (which needs to be rewritten in
-IC:/cygwin/home/build/...) for instance.
cccl helps but is rather incomplete compared to wgcc. Moreover, neither 
wgcc nor
cccl set the proper environment variables to be able to run cl.exe (which
returns 53 if any of them is wrong, eg if the PATH isn't ;-separated or
contains forward slashes instead of backslashes etc...) and to use MS
PlateformSDK.

--
SIGOURE Benoit aka Tsuna
  _____
 /EPITA\ Promo 2008, LRDE