| commit | f8a94b9decf4c76c217342ce31a05ec30cfb77e8 | [log] [tgz] |
|---|---|---|
| author | Nikhil Marathe <nikhilm@dropbox.com> | Mon Jun 29 01:43:00 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 29 01:43:57 2020 -0700 |
| tree | 016891bc7870b55d8b3bca5ecb2349dd0ace9247 | |
| parent | d101fc87b65ff45f87bccfdf93c2bdbddd7dc4f5 [diff] |
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
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
