tree 016891bc7870b55d8b3bca5ecb2349dd0ace9247
parent d101fc87b65ff45f87bccfdf93c2bdbddd7dc4f5
author Nikhil Marathe <nikhilm@dropbox.com> 1593420180 -0700
committer Copybara-Service <copybara-worker@google.com> 1593420237 -0700

Restore macOS 10.10 version compatibility to Bazel

This is part of the fixes for #11442. (Not a complete fix because it does not address the bazel 2 branch).

It makes the macOS deployment target 10.10. Then it wraps the calls to the macOS logging infrastructure so they only execute on macOS 10.12+.

I've tested this change and a similar cherry-pick on tag 2.2.0 and confirmed this results in a functioning Bazel (at least for the targets we build) on macOS 10.10.

I have questions around what I can do better:
1. I have just added a universal .bazelrc entry. Is there some way to gate this to just macOS in the Bazel infrastructure? Is that even necessary?
2. The Bazel tagged versions are just tags and not branches, which means I cannot submit a PR for a backport to Bazel 2.2. How would you like to handle this?

Closes #11565.

PiperOrigin-RevId: 318770522