OpenSSL and -debug-and-release: How to specify correct libs?
qtacc32 last edited by qtacc32
I am using Visual Studio 2013 and want to build Qt in debug and release mode with -openssl option.
I have built the openssl libraries already in both debug and release mode.
So I have now:
...\openssl1.0.2a\lib with four library files:
(I appended a d to the debug versions)
But is this correct? When building Qt with -debug-and-release, will it choose the right libraries or use the openssl release versions for both debug and release build?
I have also configured with: -I ...\openssl1.0.2a\include -L ...\openssl1.0.2a\lib
I just don't know if this is sufficient, but how to tell Qt to use libeay32d.lib/ssleay32d.lib for its debug build and libeay32.lib/ssleay32.lib for its release build for example?
Thank you very much!
Oh, I guess when not using -openssl-linked, it will not matter as the .lib files will not be used.
I'm still interested in what to do if I'd actually want to use -openssl-linked.
qtacc32 last edited by
This post is deleted!