Yes, I was surprised too. I don't know if it's because Cygwin's ar has been made compatible with Microsoft's lib format, or if the two formats have always been the compatible.
One advantage of using gcc2cl is that you don't need to worry about most of the Microsoft specifics such as .obj vs .o. As I mentioned I recall the only changes required in addition to constructing the CygwinMSVC Configure entry was to rename INCLUDE/LIB in the Makefile's; and a do_win32_shared is also required. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Polyakov Sent: Wednesday, 12 May 2004 10:17 PM To: [EMAIL PROTECTED] Subject: Re: Win32 compiles under cygwin > 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] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
