commit | d56dc18e1978102e35fbcf92c5d63f9f9eef37cd | [log] [tgz] |
---|---|---|
author | Keith Smiley <keithbsmiley@gmail.com> | Thu Mar 09 23:13:48 2023 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 09 23:15:20 2023 -0800 |
tree | 31dd25c196ed1aa839031b5c5f3ac3635f402ec9 | |
parent | f057c7408a60cb9955a95d02e9e9a05760bd1f13 [diff] |
Move Apple toolchain setup to apple_support This moves the CC toolchain for building Apple platforms besides macOS to the apple_support repo https://github.com/bazelbuild/apple_support/pull/113 The default unix toolchain is now used if someone wants to build for macOS without the apple_support toolchain, but it doesn't handle as many platform specific features as the previous toolchain. Fixes https://github.com/bazelbuild/bazel/issues/15041 Closes #16619. PiperOrigin-RevId: 515546196 Change-Id: Ia54b53e7093c1edbfe8276730aaed5a11a94a027
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md