Runfiles propagation for cc_shared_library

[bd-tkoolen]

While trying to switch from the cc_binary(..., linkshared = 1) way of creating standalone shared libraries to using the cc_shared_library rule, I noticed that cc_shared_library doesn't propagate the runfiles from its deps like cc_binary does.

Here is a sketch:

cc_library(
    name = "cc_lib",
    srcs = [ "lib.cpp" ],
    hdrs = [ "lib.hpp" ],
    data = [ "data.txt" ]
)

cc_binary(
    name = "cc_bin",
    linkshared = 1,
    deps = [ ":cc_lib" ],
)

cc_shared_library(
    name = "cc_shared_lib",
    deps = [ ":cc_lib" ],
)

sh_binary(
    name = "foo",
    srcs = ["foo.sh"], # empty executable file
    data = [":cc_shared_lib"],
    # data = [":cc_bin"],
)

If I comment out data = [":cc_shared_lib"], and uncomment data = [":cc_bin"], in the sh_binary and bazel run it, data.txt appears in the runfiles, which wasn't present with just the cc_shared_lib dependency.

Is this an intentional design? If so, what is the reason behind it?

[meteorcloudy]

/cc @oquenchil

[oquenchil]

This isn't intentional as far as I can recall.