| commit | 88771830d92a93027ed7dfb5d130b3311400dbc4 | [log] [tgz] |
|---|---|---|
| author | Ian (Hee) Cha <heec@google.com> | Mon Feb 05 23:02:05 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 05 23:03:52 2024 -0800 |
| tree | 248d227fe796380a331060c451acd3b00aa4e241 | |
| parent | 5ab21e057775909c746249078705d7e7f4cbfe0a [diff] |
Mark gcc-<version> as `gcc` instead of `compiler` in Unix CC toolchain Fixes #17794 I was looking at writing a test for this, but not sure how you'd like me to go about that. Hard-code a gcc, e.g. `gcc-11`, or search the `$PATH` for a `gcc-<version>`? Closes #20350. PiperOrigin-RevId: 604543138 Change-Id: I71ebbac77e4e32ebc5d99ec4a81415727af12cbc
{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
