| commit | d6da8a62f12811e462c9a0653ddb826fea3b5074 | [log] [tgz] |
|---|---|---|
| author | armandomontanez <amontanez@google.com> | Tue Dec 09 07:59:50 2025 -0800 |
| committer | GitHub <noreply@github.com> | Tue Dec 09 15:59:50 2025 +0000 |
| tree | d0d8bbe938adf135e50aee4d021c09ea8ca4b0b6 | |
| parent | 3cbb3fc2b7c3c0ab055eae546741e303bb6079ff [diff] |
Do not forward ARFLAGS (#3763) This is a partial revert of #3704. It does NOT revert logic that properly finds the hermetic archiver (binary and associated tests). cc-rs needs full ownership of flag handling for the archiver. This is in part due to `ar` having very specific positional flag behaviors, and partially due to some special logic in how cc-rs constructs static libraries. The change to enable `ARFLAGS` was causing many toolchains that pass flags to the static archiver to error out due to conflicting expectations for flag handling. Example bad `ar` invocation, where `cq` is treated as the destination archive instead of the `ar` tool mode: ``` ar rcsD cq dest.a src1.o src2.o ``` This drops forwarding of `ARFLAGS` to fix the common case.
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.