| commit | a212e4fd656a0d72e195e0bb79546fef287a18f1 | [log] [tgz] |
|---|---|---|
| author | PikachuHy <pikachuhy@linux.alibaba.com> | Fri Jun 14 07:58:46 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 14 08:02:03 2024 -0700 |
| tree | 85e2c69f8d3213e4221ab9e2873dd7acfaf3afac | |
| parent | a06abca4684703e677d3898086b36d4330d4a17c [diff] |
add dependency_file_feature on macos features This patch add `dependency_file_feature` to features when OS is macos. the feature `dependency_file_feature` added by default through `CppActionConfigs.java getLegacyFeatures` https://github.com/bazelbuild/bazel/blob/0dbfaccaf5bee5ea7f11c01db1fc0cd1ca7f3810/src/main/java/com/google/devtools/build/lib/rules/cpp/CppActionConfigs.java#L93-L117 ## Background I modified `tools/cpp/unix_cc_toolchain_config.bzl` and found `dependency_file` not work on MacOS when testing https://github.com/bazelbuild/bazel/pull/19940 with new action name `c++20-deps-scanning` and `c++20-module-compile`. After adding `dependency_file_feature` to features, it works. cc @comius Closes #22717. PiperOrigin-RevId: 643345857 Change-Id: I50210592edd1082e2328c7e4ab68bd0c76087aaa
{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
