| commit | c435cf4478fc6e097edc5dba0e71de6608ab77d8 | [log] [tgz] |
|---|---|---|
| author | Nick Rebbok <irebbok@outlook.com> | Thu Feb 10 19:40:02 2022 +0300 |
| committer | GitHub <noreply@github.com> | Thu Feb 10 11:40:02 2022 -0500 |
| tree | 186927e03435acc62de35f6960be76644e2244fa | |
| parent | bbccf77928c448f2ed136bb417f8f0affaa18ac8 [diff] |
propagate buildscript link search paths to parent crate (#1123) Adds a new `link_search_paths: File` field to `BuildInfo` provider. Resolves #859 I use native Windows bindings through [windows-rs](https://github.com/microsoft/windows-rs) crate and it fails to link without propagating the link search path to a platform-dependent native library. The bindings call for a native library via `#[link(name = "windows")]` and propagate search path by a buildscript from a dependency (i.e. a transitive dependency for a root crate). Propagating link search paths seems to be what is cargo doing.
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.