cmake: check USE_WINDOWS_SSPI when adding secur32 to CURL_LIBS

Instead of CURL_WINDOWS_SSPI.

When running CMake on Windows with no additional parameters (ie default
build configuration), the generated project files do not include the
`secur32.lib` library in the linker settings. This is because
the relevant check was looking at `CURL_WINDOWS_SSPI` instead of
`USE_WINDOWS_SSPI`.

`USE_WINDOWS_SSPI` is enabled when building with SChannel (the default
on Windows), or if `CURL_WINDOWS_SSPI` is specified on the command line.

Follow-up to 0d71b18153 #17413

Closes #17728
This commit is contained in:
Joel Depooter 2025-06-23 18:14:24 -07:00 committed by Viktor Szakats
parent 8c9a9b87c2
commit c153d9eadf
No known key found for this signature in database
GPG Key ID: B5ABD165E2AEF201

View File

@ -1978,7 +1978,7 @@ if(WIN32)
endif()
list(APPEND CURL_LIBS "${_win32_crypt32}")
endif()
if(CURL_WINDOWS_SSPI)
if(USE_WINDOWS_SSPI)
list(APPEND CURL_LIBS "${_win32_secur32}")
endif()
endif()