MSVC status

[Peter Rosin]

Hi!

Christopher Hulbert asked for some MSVC status in a private message,
but I figured more people might be interested. So, I'm posting a
testsuite log from libtool master.

It was configured with:

../configure \
CC="/c/cygwin/home/peda/automake/git/automake/lib/compile cl" CFLAGS="-MD -Zi 
-EHsc" \
CXX="/c/cygwin/home/peda/automake/git/automake/lib/compile cl" CXXFLAGS="-MD -Zi 
-EHsc" \
LD=link NM="dumpbin -symbols" STRIP=: \
AR="/c/cygwin/home/peda/automake/git/automake/lib/archive lib" RANLIB=: F77=no 
FC=no GCJ=no

Don't be fooled by /c/cygwin in the above paths, or in the log for that
matter. This was all using MSYS/MSVC. /c/cygwin is just where the files
live on my system.

I do not have automake installed in my MSYS environment, so there are
a fair number of skips caused by that. I also did not run the old
testsuite as it has to many variables that are not imported correctly
from dlls.

The compile script above is from the master branch of automake, and
the archive script is from this pending automake patch:
http://www.mail-archive.com/address@hidden/msg02374.html

(Note that the final name of the latter script might not be 'archive')

Further, there are two things left todo, that were done in the old
pr-msvc-support branch that I have identified so far.

1. libtool needs to support archivers with @FILE support, since
libtool currently falls back to piecewise linking for long
command lines. MSVC doesn't support piecewise linking. I have a
patch sitting on disk that I fiddle with from time to time, expect
it to appear on a list near you when the above pending automake
patch is commited, if not sooner.

2. Support for other C++ file extensions, MSVC only handles .cpp
files as C++ code without feeding it a hint. But this change is
best done in the compile script so it's a thing for automake...

Anyway, I have attached a full testsuite log.

Cheers,
Peter

testsuite.log.bz2
Description: Binary data