Hi Giuseppe,
> Ray Satiro <[email protected]> writes: > >> Also I notice the changes in 2533 require static openssl libs for testing >> checking for EVP_MD_CTX_init in -leay32... yes >> checking for SSL_connect in -lssl32... yes >> configure: Enabling support for SSL via OpenSSL (shared) >> checking for libssl... no >> configure: error: --with-ssl=openssl was given, but SSL is not available. >> >> I think regardless of whether libssl is there if eay32 and ssl32 are there > then it should link to the dlls and not need to test ssl and crypto. > > I would like to keep the mingw specific tests to a minimum level and use > more generic checks as much as possible, then my hope was to switch to > checks to test used already on other platforms after I set mingw > specific stuff. Do you haev any suggestion for it? I am all ears. What I was saying is that once the configure script confirms that OpenSSL shared is available and tests ok then those other tests are not needed for mingw, in my opinion. This is assuming shared is intended to be preferred over static. With Windows builds I would expect that's the case, if using openssl to use the DLLs by default. An example of this is in revision 2485 configure.ac changes. There was a case for mingw, and then the default case. Now there is no default case, and the script will always try for static even if shared has already been found. J
