-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmake // build issue when OpenSSL enabled on Windows and schannel detected #617
Conversation
By analyzing the blame information on this pull request, we identified @jzakrzewski, @billhoffman and @Sukender to be potential reviewers |
a7ae284
to
cf66976
Compare
@bradking Could you please review? |
mark_as_advanced(CMAKE_USE_OPENSSL) | ||
|
||
if(WIN32) | ||
CMAKE_DEPENDENT_OPTION(CURL_WINDOWS_SSPI "Use windows libraries to allow NTLM authentication without openssl" OFF | ||
"CMAKE_USE_OPENSSL" ON) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC the goal is to present the CURL_WINDOWS_SSPI
option (with default ON
) when CMAKE_USE_OPENSSL
is OFF
(default). When CMAKE_USE_OPENSSL
is ON
then CURL_WINDOWS_SSPI
should be non-optional and forced to OFF
. In that case the dependent option should be:
CMAKE_DEPENDENT_OPTION(CURL_WINDOWS_SSPI "Use windows libraries to allow NTLM authentication without openssl" ON
"NOT CMAKE_USE_OPENSSL" OFF)
@bradking updated per your comments with snikulov@b2e6d0a If it looks OK for you - I'll squash it into single commit. |
Yes, LGTM. |
b2e6d0a
to
9a7486e
Compare
@bagder I'm done. |
thanks! |
Options OpenSSL and Windows Schannel should be exclusive.
Enabling them both will break the build - we got redefinition in
ssl_connect_data
structure (ref to Appveyour buils).So on Windows I disable CMAKE_USE_OPENSSL by default (Windows Schannel is preferred).
But we always can override this option with
cmake .. -DCMAKE_USE_OPENNSSL=ON
| OFF