…cks are done. LIBS are set back to original value if all crypto checks for that implementation fail.
… that used in the cmake build system.
…_WIN. Defines will be added from confdefs.h which is generated while configure script executes.
…pport. On Windows, if the static libraries for PCRE are to be used and the PCRE static libs were built using the mingw toolchain, libgcc must also be linked for resolving the symbol ___chkstk_ms.
…raries built using mingw toolchain.
Checks will now be similar to checks done with autotools, where all defines are passed into a source file along with the append source code to be checked. Also, once a library that support a crypto function is found, all other checks for that crypto function will be skipped.
Windows port of libbz2 cannot use AC_CHECK_LIB. See https://mail.gnome.org/archives/gnumeric-list/2008-November/msg00038.html for an explanation.
This will ensure documentation is actually generated when building release tarballs.
…pport. New ordering is now LIBC followed by LIBREGEX followed by LIBPCREPOSIX.
…r expressions. AUTO means choose the first suitable library The other options are LIBPCREPOSIX, LIBC, and LIBREGEX.
… and library.
… Windows build. This will allow using WINVER for VISTA and up so that crypto checks for SHA256, SHA384, and SHA512 will pass.