libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: MSYS+MSVC for libtool branch-2-0


From: Peter Ekberg
Subject: RE: MSYS+MSVC for libtool branch-2-0
Date: Sat, 28 May 2005 20:47:10 +0200

Ralf Wildenhues wrote:

[snip]

> > Perhaps libname_spec should be just $name on MSVC? Instead
> > of doing that, I added a second very similar loop in
> > ltmain.sh, but that might be a cludge?
> 
> Need to look at this closer.

I had a second look, and if I do

  libname_spec='$name'

for MSVC in libtool.m4, instead of the usual

  libname_spec='lib$name'

this snippet in ltmain.m4sh, for file_magic*), line approx 4750,

  if test -n "$a_deplib" ; then
    libname=`eval "\\$ECHO \"$libname_spec\""`
    for i in $lib_search_path $sys_lib_search_path $shlib_search_path;
do
      potential_libs=`ls $i/$libname[[.-]]* 2>/dev/null`
      for potent_lib in $potential_libs; do
        # Follow soft links.
        if ls -lLd "$potent_lib" 2>/dev/null |

has problems because shell expansion (?) of $i/$libname[.-]*
is not case insensitive.

If I e.g. supply -L/msvc/lib -lwsock32 and there's a file
WSOCK32.LIB in that dir, the ls command will not find it.

Using -lWSOCK32 works, but that does not work for MinGW
and Cygwin, since they provide libwsock32.a with the
same functionality as WSOCK32.LIB in MSVC. So, to not
make makefiles a mess, I'd really like the above to include
/msvc/lib/WSOCK32.LIB in potential_libs.

Any suggestions on how to make that happen?

Cheers,
Peter




reply via email to

[Prev in Thread] Current Thread [Next in Thread]