| commit | 0e0241e9b0e4122f1e28a1ca0d358dd987f21971 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@gmail.com> | Fri Feb 23 02:27:34 2024 -0800 |
| committer | GitHub <noreply@github.com> | Fri Feb 23 10:27:34 2024 +0000 |
| tree | 9b7ffe4b3f7ba70fe5e3cc4cdfa3c7a6a2c3c589 | |
| parent | cf5f0bd888aaf576978ccc16a3fbf8cecaaf0d52 [diff] |
Introduce rules_rust_unsupported_feature (#2511) Add a special sentinel feature name to the UNSUPPORTED_FEATURES list. This feature name can be used by authors of C++ toolchain configurations to house any configuration fragments (e.g., linker flags) that should NOT be applied when linking Rust targets. The specific motivation for this is that I'm working on a project that includes `-fsanitize=address` in its clang configuration. This needs to be disabled when linking Rust. I tried the more straightforward approach of adding the `features` attribute to `rust_binary` targets in my repo, but this is not sufficient: a `rust_binary` has implicit deps on targets like @rules_rust//util/process_wrapper:bootstrap_process_wrapper.
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.