| commit | b272cef7d4b2d1be4e3f82b737c3c14d5e768aea | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Fri Dec 02 06:19:33 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Dec 02 06:21:13 2022 -0800 |
| tree | fa9e0be0e637771ba9d9e330542d3a9096a2bae0 | |
| parent | a556969326107423738fbf8a80bad9aaf9935578 [diff] |
Add auto-configured Unix toolchain support for `BAZEL_CONLYOPTS` Since `BAZEL_CXXOPTS` is only used for C++ compilation, there was no way to pass in options for C compilation that would also be used when discovering built-in include directories with `-xc`. When using the non-Xcode auto-configured toolchain on macOS, it can be necessary to specify the macOS SDK sysroot via a compiler flag. While this can usually be achieved by combining `--conlyopt` with `BAZEL_CXXOPTS`, this assumes that the built-in include directories returned with `-xc` are always a subset of those returned with `-xc++`. Having `BAZEL_CONLYOPTS` allows this situation to be navigated in a way that is clearly correct. Also adds test coverage for `BAZEL_CXXOPTS`. Closes #16839. PiperOrigin-RevId: 492452434 Change-Id: I72fbe25da22f3c3ca3be9e52bbf0c5fe1d0828ac
{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
