Hello, I am trying to compile GRPC without BoringSSL. Looks like this is supported via cmake. Is there a way to also support it via Bazel? My current understanding is that the Bazel build unconditionally depends on @boringssl//:ssl.
We are using Bazel to build a custom binary that links in aws-cpp-sdk and grpc. It seems like aws-cpp-sdk wants openssl while grpc seems to want boringssl. We are currently exploring defining a fake `boringssl` local_repository which has a single target (`@boringssl//:ssl` which points to system provided openssl). Would love to know if this is likely to be a fool's errand. Regards! -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/09c0b82b-cf81-438d-b096-d2df287a5cee%40googlegroups.com.
