vitalyd

Curious if anyone has thoughts on this topic? The current annoyance, from my standpoint, is the need to specify `--relocation-model=static` for `rust_binary` targets so they can link property against `cc_library`...

Just a quick link drop - [this](https://github.com/bazelbuild/bazel/blob/9bcc5a323eedf6b59d64e2325abff9fe8b548936/src/main/java/com/google/devtools/build/lib/rules/cpp/CppHelper.java#L528) appears to be the code in bazel cpp rules that determines PIC'ness based on (among other things) the compilation mode.

@acmcarther, curious - how do you guys handle this at Google (assuming you're using rules_rust there)?

FWIW, I agree with @jglick that this warning should be (at a minimum) disabled when targeting jdk 17+. It doesn’t make sense to suggest using a deprecated-for-removal API.