-
-
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: fix curl-config --static-libs #852
Conversation
By analyzing the blame information on this pull request, we identified @billhoffman, @jzakrzewski and @Sukender to be potential reviewers |
I'd like a second cmake fluent person to +1 this PR before I consider merging it. @snikulov perhaps? |
@bagder Will check it soon. |
@bradking Could you also take a look on this PR? |
Not really useful for MS platform, because of sh script. For me only one line is fine, where the message is removed. |
Does |
@bradking Oh, passing |
@Lekensteyn yes, passing the absolute path is universally supported. CMake tries to do this whenever possible because it ensures that the desired library file is used instead of just hoping that |
The `curl-config --static-libs` command should not output paths like -l/usr/lib/libssl.so, instead print the absolute path without `-l`. This also removes the confusing message "Static linking is broken" which was printed because curl-config --static-libs was disfunctional even though the static libcurl.a library works properly. Fixes curl#841
4192146
to
95ad190
Compare
Sorry for the delay, I have updated the patch according to @bradking's suggestion and now
This should work better. |
LGTM. |
@Lekensteyn Yes. LGTM. |
Applied in 2f3feda |
Libraries for
curl-config --static-libs
are required to have the form-ldl. Assume library paths like /usr/lib/libssl.so and map it to "ssl"
for curl-config.
This removes the confusing messag "Static linking is broken" which was
printed because curl-config --static-libs was disfunctional while the
static libcurl.a is fine.
Fixes #841