Include link_deps in Rust runfiles (#4204)

## Summary

- merge default runfiles from `link_deps` into Rust target runfiles
- include dynamic libraries supplied through `link_deps` alongside those
from `deps`

## Why

`link_deps` participates in native linking, but its runfiles and dynamic
libraries were omitted when `rustc_compile_action` assembled runtime
files. Binaries and library targets that link native dependencies
through `link_deps` could therefore be built successfully while missing
required runtime artifacts.

## Impact

Rust binaries, `cdylib`s, and `staticlib`s now carry the runtime files
needed by dependencies declared through `link_deps`.

## Validation

- `bazel test //test/unit/link_deps:all`
- `git diff --check`
1 file changed
tree: 143c4fa7611d58a2f23ef1fe3333334cd1f4ff9c
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cargo/
  5. crate_universe/
  6. docs/
  7. examples/
  8. extensions/
  9. ffi/
  10. nix/
  11. rust/
  12. test/
  13. tools/
  14. util/
  15. .bazelignore
  16. .bazelrc
  17. .clang-format
  18. .clippy.toml
  19. .envrc
  20. .gitattributes
  21. .gitignore
  22. .pre-commit-config.yaml
  23. .prettierrc.toml
  24. .rustfmt.toml
  25. .typos.toml
  26. ARCHITECTURE.md
  27. AUTHORS
  28. BUILD.bazel
  29. CODEOWNERS
  30. COMPATIBILITY.md
  31. CONTRIBUTING.md
  32. CONTRIBUTORS
  33. LICENSE.txt
  34. MODULE.bazel
  35. README.md
  36. version.bzl
  37. WORKSPACE.bazel
README.md

Rust Rules

  • Postsubmit Build status

Overview

This repository provides rules for building Rust projects with Bazel.

Starter repo

The fastest way to try this in an empty project is to click the green “Use this template” button on https://github.com/bazel-starters/rust.

Community

General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.

Documentation

Please refer to the full documentation.