| commit | 1456361e1b471e635e6ab02d4553978e860a69e1 | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Tue Feb 21 00:57:38 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 21 00:58:46 2023 -0800 |
| tree | cc9cd4c60335013382b3b0c5132f77468ba22631 | |
| parent | ae7cfa59461b2c694226be689662d387e9c38427 [diff] |
Set right default value for the cc_shared_library flag Without that flag being True half the motivation for the existence of cc_shared_library disappears since the rule won't perform any checks for libraries that are linked more than once. The default must therefore be True. The flag can be kept around for projects that may want to introduce the rule into their builds first then solve the duplicated linking issues as a next step. But usage of the flag is not necessary at all even for existing builds. The flag was in fact introduced with True as default value but when it was moved from being written as Starlark configuration to being part of CppOptions it was mistakenly changed to False. This change also deletes the obsolete experimental_enable_target_export_check flag. PiperOrigin-RevId: 511126574 Change-Id: I18f4a63735febea20f1ca1b74d74acdece71740a
{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
