| commit | daff327ea7923cf4032a52f6b63a44856dbeb0b8 | [log] [tgz] |
|---|---|---|
| author | scentini <rosica@google.com> | Fri Jul 15 13:12:14 2022 +0000 |
| committer | GitHub <noreply@github.com> | Fri Jul 15 13:12:14 2022 +0000 |
| tree | a8b852486e5f59c2b5ca6e514c3536dea78b0889 | |
| parent | adc80a301d8f144c8e5ac29fe377e7423417baee [diff] |
Stamp only binaries by default (#1452) Currently we pass `bazel-out/volatile-status.txt` to all the `Rustc` actions, which is bad for remote caching with `--stamp`enabled. This PR makes only `rust_binary` be affected by the `--stamp` flag by default. The rest of the rust rules have `stamp = 0` as a default. Should you want to force stamp you can set `stamp = 1`. If you want to make your target stamp behavior depend on the `--stamp` command line flag, use `stamp = -1`. Additionally, this PR makes `rules_rust` also use the stable keys for stamping, by passing `bazel-out/stable-status.txt` to the relevant `Rustc` actions when stamping is enabled. This makes `rules_rust` adhere to the contract described here: https://docs.bazel.build/versions/main/user-manual.html#flag--workspace_status_command
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.