-
Notifications
You must be signed in to change notification settings - Fork 36
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
Linking against gRPC::grpc++ vs gRPC::grpc++_unsecure #61
Comments
As an immediate workaround you can set the CMake variable I changed it because I though that |
Thank you for the quick response! I'll try that, thanks.
Yeah, and there is not a lot of documentation what those different grpc targets are and when to use what. It doesn't even lead to link errors, when both are linked in the same binary, it just leads to grpc calls hanging indefinitely. This is the issue that happens in that case: grpc/grpc#24422 (comment) |
I will change the default linkage back to Did my suggestion regarding |
Thank you, sounds great! To be honest, I have yet to try |
Asio-grpc v3 now links with |
Cool, thank you! I'll look into migrating to v3 |
Hi,
we have a project that already uses grpc and we link against
gRPC::grpc++
. We now want to introduce asio-grpc, which links againstgRPC::grpc++_unsecure
when using the generated asio-grpcConfig.cmake. This leads to problems, apparently it is not possible to link against both targets in the same binary.I found this commit: 2731e5b
So first of all the question would be: Why was this changed? Why is the default the _unsecure target?
We can fix our build by manually patching the
asio-grpcConfig.cmake.in
file and making sure that asio-grpc also links againstgRPC::grpc++
, but this is quite ugly and will break on any changes to that file.Would it be possible to add a cmake config variable so that we can optionally link asio-grpc against
gRPC::grpc++
instead of the default ofgRPC::grpc++_unsecure
?The text was updated successfully, but these errors were encountered: