Re: MSYS+MSVC for libtool branch-2-0, take 2

[Ralf Wildenhues]

Hi Peter,

I've tried your patch now, with cygwin and this version:

| Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
| Copyright (C) Microsoft Corporation 1984-2002. All rights reserved.

configured like: CC=cl CXX=cl.

Notes:

`link -LIB' can be a problem if the cygwin `link' (to create hard links)
comes before the win32 paths.  `LIB' works here.

`LIB -EXTRACT' needs Windows paths for lib and extraction directory.
With cygwin, `cygpath -w' works.  But the result needs to be properly
quoted for func_show_eval, if that is to be used.

After working around these, the next failure is when linking libltdl:

| libltdl_la-ltdl.obj : error LNK2019: unresolved external symbol 
_lt_libltdl_LTX_preloaded_symbols referenced in function _lt_dlinit.
| .libs/ltdl-6.dll : fatal error LNK1120: 1 unresolved externals

because that thing is called `_lt_ltdl_LTX_preloaded_symbols' now that
libname_spec changed.  This is probably a bug in our build which
hardwires 
  libltdl_la_CPPFLAGS = -DLTDLOPEN=libltdl
but OTOH I'm not convinced yet that the libname_spec change is correct.

The `mv' command in this line
| +      _LT_TAGVAR(archive_cmds, $1)='$CC -o $lib $libobjs $compiler_flags 
`$ECHO "X$deplibs" | $Xsed -e '\''s/ -lc$//'\''` -link -dll~linknames=~mv 
.libs/${libname}`$ECHO "X${release}" | $Xsed -e +s/[.]/-/g`${versuffix}.lib 
.libs/${libname}.lib'

is also broken w.r.t lib name.

Other than that, the HEAD convenience archive tests pass with this.  :)
Libtool's legacy test suite does too much with absolute paths which
kills my path workaround (a symlink in /tmp to my real $HOME which has
spaces in its name).

How do I get sensible information about what's in a dll (except trying
to link against it)?  (I really know little about win32.)

Cheers,
Ralf