| commit | e487a4c0f7063570d17d929e2fc82acc2a2aaacb | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Tue Jun 14 08:04:34 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 14 08:05:41 2022 -0700 |
| tree | a19d6b0c266156fad66774b1a0da03657e9b3547 | |
| parent | c068b0d2347905c5e9be793b741f693c7edb6e53 [diff] |
Add interface_library to cc_shared_library output group In general access to the interface library artifact should not be done by the user and instead the Bazel rules themselves will choose the interface library file when linking. This is possible if we use C++ rules along the whole dependency chain. However, cc_binary(linkshared=1) supported the use case where the actual files get unwrapped from the rule and it provided access to the interface library via the `interface_library` output group. This CL adds support for the same thing. This was only available on Windows for cc_binary and for now will only be available for Windows on cc_shared_library as well. RELNOTES:none PiperOrigin-RevId: 454862408 Change-Id: Iddcffa65be2bfdebac444f30d85b449ad67723e6
{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
