• Home
Name Date Size #Lines LOC

..--

env/04-Jul-2025-1411

rust/hello_world/04-Jul-2025-4322

.bazelignoreD04-Jul-20257 11

.bazelrcD04-Jul-2025519 1611

.envrcD04-Jul-2025321 85

.gitignoreD04-Jul-20259 21

BUILD.bazelD04-Jul-20251.1 KiB5147

Cargo.lockD04-Jul-2025155 86

Cargo.tomlD04-Jul-202563 55

MODULE.bazelD04-Jul-2025902 4537

README.mdD04-Jul-2025479 128

WORKSPACE.bazelD04-Jul-202536 21

WORKSPACE.bzlmodD04-Jul-202553 21

cargo_test.shD04-Jul-20251.2 KiB4723

helloD04-Jul-2025386.8 KiB

rustc_test.shD04-Jul-20251.1 KiB4123

rustfmt_test.shD04-Jul-20251.2 KiB4121

README.md

1# rules_rust with bazel_env
2
3This example uses [bazel_env.bzl](https://github.com/buildbuddy-io/bazel_env.bzl) to
4provide `cargo`, `cargo-clippy`, `rustc` and `rustfmt` from the bazel toolchains
5to the user. They will be available directly in the PATH when the user
6enters this directory and has [direnv](https://direnv.net/) set up.
7
8Advantages:
9
10- The user doesn't have to install the toolchains themselves.
11- The tool versions will always match exactly those that bazel uses.
12