Repository navigation
cmake: libcurl.pc uses absolute library paths #6169
Description
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.
Activity
reddwarf69 commentedon Nov 4, 2020
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
KNOWN_BUGS: cmake libcurl.pc uses absolute library paths
cmake: Fix libcurl.pc and curl-config library specifications
cmake: fix libcurl.pc and curl-config library specifications