| commit | 32d2f622f28dac923b4adc90185db1d65f1d0bf7 | [log] [tgz] |
|---|---|---|
| author | Googler <messa@google.com> | Fri Jul 26 11:00:22 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 26 11:01:24 2024 -0700 |
| tree | 132252df1371a713ce6c29537bbdba97b50efcae | |
| parent | ad53147cc4f4d47c064845ec9612876161ff139e [diff] |
Update `--compile_one_dependency` heuristics for header-only libraries Previously, if a header was part of a header_only library :a, then `--compile_one_dependency` would prefer to choose :b which depends on `:a`, rather than `:a` itself. After this change, it will generally prefer `:a`, unless parse_headers is turned off specifically in this package (in which case it is likely that a.h can only be understood in the context of `b.cc`). RELNOTES: `--compile_one_dependency` selects header-only `cc_library`s in more cases PiperOrigin-RevId: 656460540 Change-Id: Iba70dddd1610a78d71c05274d77d479c84efade7
{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
