Linking against gRPC::grpc++ vs gRPC::grpc++_unsecure about asio-grpc

[Tradias]

As an immediate workaround you can set the CMake variable ASIO_GRPC_DISABLE_AUTOLINK before calling find_package/add_subdirectory for asio-grpc. Then it won't link with anything.

I changed it because I though that _unsecure is the baseline and that everything else depends on it. Seems like that is not the case.

[reusing-code]

Thank you for the quick response!

I'll try that, thanks.

I changed it because I though that _unsecure is the baseline and that everything else depends on it. Seems like that is not the case.

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)

[Tradias]

I will change the default linkage back to gRPC::grpc++ in v3 of asio-grpc and let power users utilize ASIO_GRPC_DISABLE_AUTOLINK + gRPC::grpc++_unsecure as they see fit.

Did my suggestion regarding ASIO_GRPC_DISABLE_AUTOLINK work for you?

[reusing-code]

Thank you, sounds great!

To be honest, I have yet to try ASIO_GRPC_DISABLE_AUTOLINK , currently still working with my ugly workaround.

[Tradias]

Asio-grpc v3 now links with gRPC::grpc++ by default. I am also changing that in conan-center conan-io/conan-center-index#22910.

[reusing-code]

Cool, thank you! I'll look into migrating to v3