Skip to content

cmake: Check USE_WINDOWS_SSPI instead of CURL_WINDOWS_SSPI when adding secur32 to CURL_LIBS#17728

Closed
JDepooter wants to merge 1 commit intocurl:masterfrom
JDepooter:cmake_missing_secur32
Closed

cmake: Check USE_WINDOWS_SSPI instead of CURL_WINDOWS_SSPI when adding secur32 to CURL_LIBS#17728
JDepooter wants to merge 1 commit intocurl:masterfrom
JDepooter:cmake_missing_secur32

Conversation

@JDepooter
Copy link
Contributor

@JDepooter JDepooter commented Jun 24, 2025

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 0d71b18 #17413

Copy link
Member

@vszakats vszakats left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch.

It's a regression from 0d71b18 #17413 in this release cycle.

@vszakats vszakats closed this in c153d9e Jun 24, 2025
@vszakats
Copy link
Member

Thank you, merged!

@vszakats vszakats added the Windows Windows-specific label Jun 24, 2025
@JDepooter JDepooter deleted the cmake_missing_secur32 branch June 24, 2025 17:29
whrvt added a commit to neomodnet/neomod that referenced this pull request Jul 22, 2025
maybe these are related?
curl/curl#17728
curl/curl#17982
curl/curl#17979

idk what the downsides of this are though
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants