| commit | 33e7261234173fe5f4b6ce12035beeba74d7ae77 | [log] [tgz] |
|---|---|---|
| author | Alessandro Patti <ale812@yahoo.it> | Wed May 25 04:24:32 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 25 04:26:11 2022 -0700 |
| tree | 23431b81e088b5c27425bc2340af5c1bf16b0ea1 | |
| parent | 60bfd1879d19366b0c369a9db472ca107ab77d61 [diff] |
Add archiver flags to cpp crosstool config There are three changes proposed in this pr that do not alter the current behaviour but that allow more flexibility when defining a toolchain: - Move default macos archiver flags from [CppActionConfigs.java#L622](https://github.com/bazelbuild/bazel/blob/feea781b30788997c0b97ad9103a13fdc3f627c8/src/main/java/com/google/devtools/build/lib/rules/cpp/CppActionConfigs.java#L622) to the crosstools definition. - Add `archive_flag` attribute to allow passing additional flags to the archive action. - Add libtool feature to switch between macos `libtool`'s flags and `ar`'s. Closes #14873. PiperOrigin-RevId: 450893196 Change-Id: Ibbbc6383d69c453fd8e86aee2c7399ee9988fa22
{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
