| commit | 8ba5eed4ef5cb1636df5b8effd940290ad890b1c | [log] [tgz] |
|---|---|---|
| author | trybka <trybka@google.com> | Wed Apr 13 07:12:38 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 13 07:14:09 2022 -0700 |
| tree | 08f6a50a40812bc844c95cdf7381ccd3d700e991 | |
| parent | 591dcc45b9c567aa18bd08c893323258a10068c9 [diff] |
## Add support for Windows `linkstatic` computed default This uses the same technique as `cc_binary` with/without aspects. Essentially we are declaring two rules named cc_test with different private attribute defaults. This is primarily done this way to hide the implementation details of computed defaults until something like [bazel/issues/14434](https://github.com/bazelbuild/bazel/issues/14434) is implemented. NOTE: When `cc_test` written in Starlark is made the default, this _will_ introduce a behavior change -- notably that we will default linkstatic based on whether we are _targeting_ Windows, not whether the host Platform is Windows (as is done today). The latter heuristic may have been the best available option before Platforms, but it does not match the actual intent. PiperOrigin-RevId: 441472088
{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
