| commit | 8c4b1c908e5b520126a2480b0855c0c1e58d1ae0 | [log] [tgz] |
|---|---|---|
| author | keertk <keerthanakumar@google.com> | Thu Nov 16 12:27:17 2023 -0800 |
| committer | GitHub <noreply@github.com> | Thu Nov 16 20:27:17 2023 +0000 |
| tree | aaec9bf7cb78a43ab21b5c851f8db58f99308091 | |
| parent | 6eb3a12d303df00e236528cff48e8cf3e7656197 [diff] |
[7.0.0] Fix cc_shared_library error with hdr-only libraries (#20228) Fix cc_shared_library error with hdr-only libraries cc_libraries with a linker_input with no libraries (either because they contain only headers or only linkopts) caused errors in cc_shared_libraries triggered by a check that made sure that a cc_library wasn't linked more than once into different shared libraries. That check can be ignored in those cases. RELNOTES:none Fixes #19920 Commit https://github.com/bazelbuild/bazel/commit/886b13fd00b5a17161d9558b6b11dd135355e5cb PiperOrigin-RevId: 583033207 Change-Id: I227021f33596dbc5a6708fa5a705803094f24665 Co-authored-by: Googler <gnish@google.com>
{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
