tree a19d6b0c266156fad66774b1a0da03657e9b3547
parent c068b0d2347905c5e9be793b741f693c7edb6e53
author Googler <plf@google.com> 1655219074 -0700
committer Copybara-Service <copybara-worker@google.com> 1655219141 -0700

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