Ok, I understand where you're coming from. What we have works fine, through we've not played around with Kerberos. I've created a new "CygwinMSVC" entry in Configure which uses enough of the Cygwin entry to integrate with the rest of the build framework, but uses a SYSNAME of WIN32 (not CYGWIN32) and sets other defines such as DSO_WIN32 so that it picks up the Microsoft-specific stuff.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Altman Sent: Tuesday, 11 May 2004 12:52 PM To: [EMAIL PROTECTED] Subject: Re: Win32 compiles under cygwin Since the cygwin environment is different from the MS Run Time environment, I would not make the assumption that the binaries produced use exactly the same configuration options. They may but I would not count on it. I understand what you are attempting to do; I just do not know if the results will be the same. I know that with other packages such as Kerberos you absolutely do not get the same result when building under cygwin because the environment is more Unix like and therefore different assumptions are made. Jeffrey Altman Steven Reddie wrote: >Jeffrey, > >Are you saying that using something like gcc2cl to kick off a build the >way you do for cygwin, but using the Microsoft compiler, is the wrong >way to go? It's working well for us in-house, though we've been using >static libraries up until now and are just finishing up changes to >support the DLL build. > >Mark, the naming issue is something that we need to handle also, >although we need to use a custom name with the OpenSSL version number >included. Whatever we can contribute will include support for altering >the name. > >Steven > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
