tree d7b242e7df5b0b49abb8cb16f853d22fad72fbad
parent a64352ae58134ad57a7adfbe50c28f0875b976f0
author bbaren <bbaren@google.com> 1601310367 -0700
committer Copybara-Service <copybara-worker@google.com> 1601310501 -0700

Propagate linkstamp information through `objc_library` rules

A previous change (https://github.com/bazelbuild/bazel/commit/3a28c96814e54d8e95f132a82cf501cf137d918e) made
`apple_binary` support the `stamp` attribute in the same way as
`cc_binary` does: Read linkstamp data from its dependencies’ `CcInfo`s
and add linkstamp objects to the final link. However, `objc_library` did
not propagate the linkstamp attributes from C++ dependencies into its
`CcInfo` output, so

    apple_binary(
        name = "binary",
        platform_type = "macos",
        stamp = 1,
        deps = [":cc_lib"],
    )
    cc_library(
        name = "cc_lib",
        linkstamp = "linkstamp.cc",
    )

would work fine while

    apple_binary(
        name = "binary",
        platform_type = "macos",
        stamp = 1,
        deps = [":objc_lib"],
    )
    objc_library(
        name = "objc_lib",
        deps = [":cc_lib"],
    )
    cc_library(
        name = "cc_lib",
        linkstamp = "linkstamp.cc",
    )

would fail. Correct this by having `objc_library` preserve linkstamp
data from C++ dependencies; also correct the test that was supposed to
catch this.

RELNOTES: none
PiperOrigin-RevId: 334173406