Ralf Wildenhues wrote:
> Can we get in the position that both might be used ("lib" in older,
> already installed libs, "ar" for a newer package the user is about
> to link)? I believe not, but need to check so.
I did a test run with CC=cl AR=ar (didn't keep the output, sorry),
and Microsoft link did not like (at least some) libraries created
by ar, so I guess the only viable option is to stick with AR=lib
for MSVC. The other way around (CC=gcc AR=lib) is not very
interesting, is it?
I'd also argue that you should have LD=link if you have CC=cl,
since that is what is invoked by cl.exe when it needs to link.
Should I stick a
: ${LD=link}
somewhere in some MSVC branch? (perhaps with some magic to get
link from the same dir that cl is in, Cygwin ships with a "link"
program that probably ends up before the intended Microsoft link
in the path)
strip and ranlib destroys the output from the Microsoft tools,
so that's why I configure with STRIP=: and RANLIB=:
Cheers,
Peter
