| commit | 4e593b6cc3e1dab70eed5fdec239ffc0b4179b91 | [log] [tgz] |
|---|---|---|
| author | Daniel Wagner-Hall <dwagnerhall@apple.com> | Tue Oct 29 18:22:16 2024 +0000 |
| committer | GitHub <noreply@github.com> | Tue Oct 29 18:22:16 2024 +0000 |
| tree | 60f99e20ad60de2b7090ace3da56c3a4bb3c7344 | |
| parent | c4586070fa94071a4c00792f0f693d019432077e [diff] |
Make toolchain vars available but don't automatically set them (#2969) Previously if a target depended on a toolchain which exposed `$(FOO)`, we would automatically set `$FOO` as an env var. This was not correct. Toolchains should make Make variables available for expansion in env vars, but should not automatically promote them to action env. If you want `$FOO` set, you should set `$FOO=$(FOO)` in the appropriate env var attribute.
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.