Need a potential changes tested on MinGW-64

2016-10-16 Thread trungantran
The first will break compilation if someone uses MinGW-w64 CRT with secure APIs support. This is because we have two declaration of memcpy_s imported in global namespace (line 66): USING_NAMESPACE(CryptoPP) The second also break compilation if someone uses MinGW-w64 CRT v 3.x with secure APIs s

Re: Need a potential changes tested on MinGW-64

2016-10-16 Thread Jeffrey Walton
> So I suggest a change as follow: > #if defined(__MINGW32__) > // avoid ambiguity if we have two versions of memcpy_s > #if !defined(MINGW_HAS_SECURE_API) || (MINGW_HAS_SECURE_API + 0 == 0) || > defined(CRYPTOPP_WANT_SECURE_LIB) > using CryptoPP::memcpy_s; > #else > using ::memc