Properly handle libcurl flags in CMakeLists.txt on Windows #1079
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Stumbled upon this when setting up sunshine in vscode, where I was getting strange linker errors.
In
CMakeLists.txtbothCURL_STATIC_LDFLAGSandCURL_STATIC_CFLAGSare lists, when converted to string their items get semicolon-separated.CMAKE_CXX_FLAGSis a string, where flags are space-separated.What basically happened,
CURL_STATIC_LDFLAGSwas always converted to single gibberish-Largument which just didn't trigger any errors. AndCURL_STATIC_CFLAGSwas properly converted only when the list had a single item (pkg-config --static --cflags libcurlreturned only-DCURL_STATICLIB. Whenpkg-configgets called outside of msys environment, it prepends include directory with-Iargument , andCURL_STATIC_CFLAGSbreaks exactly likeCURL_STATIC_LDFLAGS. To the end-user it looked like libcurl linking errors, because-DCURL_STATICLIBwas not set.This should fix building in vscode, and maybe some other scenarios.
CURL_STATIC_LDFLAGSare not needed, becauseCURL_STATIC_LIBRARIESare already passed totarget_link_libraries(), it's enough to set up include and library lookup directories for exotic libcurl installations.Type of Change
.github/...)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.