We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What version of protobuf and what language are you using? Version: 5.25.4 Language: C++
What operating system (Linux, Windows, ...) and version?
Alma Linux 9
What runtime / compiler are you using (e.g., python version or gcc version) gcc13
What did you do? Steps to reproduce the behavior: Configured protobuf with
-D CMAKE_BUILD_TYPE=Debug
And then try linking another project that uses pkgconfig to find protobuf
What did you expect to see
A successfully linked package
What did you see instead?
linker cannot find -lprotobuf
The problem
CMake defines a postfix for debug builds
protobuf/CMakeLists.txt
Lines 54 to 55 in 3ba0709
But the pkgconfig template does not account for this possible postfix
protobuf/cmake/protobuf.pc.cmake
Line 10 in 3ba0709
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What version of protobuf and what language are you using?
Version: 5.25.4
Language: C++
What operating system (Linux, Windows, ...) and version?
Alma Linux 9
What runtime / compiler are you using (e.g., python version or gcc version)
gcc13
What did you do?
Steps to reproduce the behavior:
Configured protobuf with
-D CMAKE_BUILD_TYPE=Debug
And then try linking another project that uses pkgconfig to find protobuf
What did you expect to see
A successfully linked package
What did you see instead?
linker cannot find -lprotobuf
The problem
CMake defines a postfix for debug builds
protobuf/CMakeLists.txt
Lines 54 to 55 in 3ba0709
But the pkgconfig template does not account for this possible postfix
protobuf/cmake/protobuf.pc.cmake
Line 10 in 3ba0709
The text was updated successfully, but these errors were encountered: