| commit | 00b57b17adcf9a76bd92d4ed0fd948bb6392d0b0 | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Fri Feb 17 08:14:45 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 17 08:15:55 2023 -0800 |
| tree | 40f98a911649df90a1e4d47f5ea00ca2a211adde | |
| parent | fa67ab9db9ff6129d7bcff48406391c65457a6d8 [diff] |
Move condition from create_linking_context_from_compilation_outputs to rules This condition influenced whether a dynamic library would be created. This change moves it to the rules so that rule authors have more flexibility in deciding what happens. RELNOTES:Custom C++ rules on Windows calling cc_common.create_linking_context_from_compilation_outputs should review whether each target of the rule type should produce a dynamic library since a condition which blocked their creation has been moved to the rules from behind the API. PiperOrigin-RevId: 510435401 Change-Id: I89c6adb32fb0c351c3d1b3912980dddca36439ef
{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
