Skip to content
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

Jump to bottom

cmake: libcurl.pc uses absolute library paths #6169

Closed
reddwarf69 opened this issue Nov 4, 2020 · 1 comment
Closed

cmake: libcurl.pc uses absolute library paths #6169

reddwarf69 opened this issue Nov 4, 2020 · 1 comment
Labels
cmake KNOWN_BUGS material

Comments

@reddwarf69
Copy link
Contributor

The libcurl.pc file generated by cmake contains things like Libs.private: /usr/lib64/libssl.so /usr/lib64/libcrypto.so /usr/lib64/libz.so. The autotools equivalent would say Libs.private: -lssl -lcrypto -lz.

Not sure of the implications. But I guess it would affect, for example, somebody who wants to use also a static version of libz.
@reddwarf69
Copy link
Contributor Author

reddwarf69 commented Nov 4, 2020 •
edited

FWIW I am personally using https://github.com/RedDwarf69/curl/tree/cmake. I'm not creating PRs because I have not tried to make it ready for that (e.g I'm increasing the minimum required cmake version... and I have no idea how much you want to keep cmake 3.2 support).
I'm solving this with reddwarf69@291e6ee

@bagder bagder added the cmake label Nov 4, 2020
bagder added a commit that referenced this issue Nov 18, 2020
@bagder
KNOWN_BUGS: cmake libcurl.pc uses absolute library paths
4c9a753 
Closes #6169
@bagder bagder closed this as completed in 1920993 Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cmake KNOWN_BUGS material
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bagder @reddwarf69