Right, I was flat out today and forgot about that, probably because I don't understand what is significant about how ar/lib is invoked. We're relying on the OpenSSL build to use Cygwin's ar and it turns out that the resulting libcrypto.a is compatible with Microsoft's tools (eg. "link ... libcrypto.a" works without a problem).
Wow! A bit unexpected, because ar is more or less general purpose archiver [at least you can pack literally whatever you wish with it]. Thanks for enlightening.
If this approach isn't wanted an ar shell script wrapper could be used which invokes lib.
As already mentioned what I find attractive is the idea of using Unix-like make.exe *alone* to produce a Visual C build. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
