[cpprestsdk] Avoid using pkg-config to find OpenSSL libraries on Linux #11694
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Correct fix would be to call cmake with Or if that does not work due to possible macro errors try: |
orudge
force-pushed
the
cpprestsdk-fix-openssl-detection
branch
from
2c118c4
to
30fcbc3
Compare
Thanks for the hint, that looks to work better. |
LilyWangL
added
category:port-feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When linking to a vcpkg-built C++ REST SDK on Linux, I noticed my executables being generated had redundant references to libssl.so.1.1 and libcrypto.so.1.1, rather than the static libraries built by vcpkg being used.
I tracked the issue down to an issue in the C++ REST SDK cpprest_find_openssl.cmake file. I have submitted a pull request to the project directly (microsoft/cpprestsdk#1438) but this should fix the issue in the mean time.