Difference in debug/release builds: error BCryptHash could not be located #4195
Unanswered
bialix-electronicus
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using msquic 2.3.0 as part of bigger ICE/STUN/TURN enabled application and have strange problem with my build. Msquic statically linked. Everything works fine on Windows 10+ in both release/debug versions. But on older Windows 8.1 debug version does not start at all with error
Of course my code checks Windows version to be at least 10 to enable QUIC feature, so there is no calls at all to msquic lib at Windows 8.1.
The strangest thing here: release version is running fine on the same Windows 8.1. Can somebody tells what's the difference in debug/release libs?
I've searched the sources and found 2 places where brypt.h API is called:
src\platform\cert_capi.c:1484 - BCryptHash (API available since Windows 10)
src\platform\crypt_bcrypt.c:734 - BCryptHashData (API available since Windows 7 I believe).
Is there any simple way to help my debug build work on Windows 8.1 even though msquic won't be enabled?
Beta Was this translation helpful? Give feedback.
All reactions