| commit | 699e40373f95e42390a85f29dfa1098636336103 | [log] [tgz] |
|---|---|---|
| author | Googler <waltl@google.com> | Wed Mar 22 07:15:40 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Mar 22 07:16:42 2023 -0700 |
| tree | 728e3c54c331a749fe0a5b9e701f5f53ae3df7a6 | |
| parent | b0fc11d8f386141d2c5efd39cbeed316d620888a [diff] |
Automated rollback of commit a50cca561fe0a77c3750101e505171ddcc16db72. *** Reason for rollback *** Roll forward with fix *** Original change description *** Automated rollback of commit d56dc18e1978102e35fbcf92c5d63f9f9eef37cd. *** Reason for rollback *** Breaks builds internally. *** Original change description *** 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 toolc *** PiperOrigin-RevId: 518560017 Change-Id: I00a106b68eac982e3d903531d5db48ae053f9301
{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
