| commit | 9d344794072cccb4eaf10cf79aaecad8bfb70ea8 | [log] [tgz] |
|---|---|---|
| author | Ed Schouten <ed@nuxi.nl> | Wed Jun 05 14:20:27 2024 +0200 |
| committer | GitHub <noreply@github.com> | Wed Jun 05 12:20:27 2024 +0000 |
| tree | b6a86aa973e144499b808d88c22c496bb32f90b2 | |
| parent | e3f6258b1e1660652ae044f01c6dac074f9fb206 [diff] |
Ensure dynamic library dependencies end up in the runfiles directory (#2671)
Right now the runfiles directory only contains "data" that is attached
to a rust_binary() or one of its dependencies. This is inconsistent with
cc_binary() and go_binary(), which also include an `_solib_*/` directory
containing shared library dependencies.
When doing a plain 'bazel run' against the resulting executable, this is
not a noticeable issue. The reason being that the runtime dynamic linker
will use `${execroot}/_solib_*`. However, it does become a problem when
`pkg_tar(include_runfiles = True)` is used to construct an archive of
the binary so that it can be placed in a container image.
This change extends the runfiles gathering logic to merge all
LibraryToLink.dynamic_library files in there as well.
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.
Please refer to the full documentation.