Hi, I'm currently in the process of adding tink-cc as a bazel dependency. I'm essentially following this guide: https://developers.google.com/tink/setup/cc#installation.
However I have a small issue; the MODULE.bazel uses boringssl, but my application is already using OpenSSL 3, and the two can't be mixed.
|
bazel_dep( |
|
name = "boringssl", |
|
version = "0.20251002.0", |
|
) |
tink-cc supports OpenSSL 3, so I'm patching the MODULE.bazel using archive_override. But that feels a bit hacky/fragile. Is there a better way, or something tink-cc could do to make workflow better?
Hi, I'm currently in the process of adding tink-cc as a bazel dependency. I'm essentially following this guide: https://developers.google.com/tink/setup/cc#installation.
However I have a small issue; the
MODULE.bazeluses boringssl, but my application is already using OpenSSL 3, and the two can't be mixed.tink-cc/MODULE.bazel
Lines 50 to 53 in 25ac091
tink-cc supports OpenSSL 3, so I'm patching the
MODULE.bazelusingarchive_override. But that feels a bit hacky/fragile. Is there a better way, or something tink-cc could do to make workflow better?