| commit | 1f9b63a408cdbd289d3289e1cf6da3abeae364e0 | [log] [tgz] |
|---|---|---|
| author | Daniel Wagner-Hall <dwagnerhall@apple.com> | Wed Sep 06 17:38:35 2023 +0100 |
| committer | GitHub <noreply@github.com> | Wed Sep 06 18:38:35 2023 +0200 |
| tree | 942d071f01437defe696aacb8fd3612bfcef1d5a | |
| parent | f74546552d7585f176a697c2d8a94c54e5ab42c8 [diff] |
cargo_build_scripts can be run from custom directories (#2152) While running from CARGO_MANIFEST_DIR is the simplest thing for compatibility, there are cases where a cargo build script may be easier to run from the exec root as most bazel actions do (e.g. where a C++ toolchain specifies in-repo include paths). This mirrors the `rundir` attribute of `go_test`, which has similar concerns: https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/rules.md#go_test-rundir
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.