This module provides a single place for all aspects, rules, and macros that are meant to have stardoc generated documentation.
Rules
rust_benchmark
Builds a Rust benchmark test.
Warning: This rule is currently experimental. Rust Benchmark tests require the Bencher
interface in the unstable libtest
crate, which is behind the test
unstable feature gate. As a result, using this rule would require using a nightly binary release of Rust.
Example:
Suppose you have the following directory structure for a Rust project with a library crate, fibonacci
with benchmarks under the benches/
directory:
[workspace]/
WORKSPACE
fibonacci/
BUILD
src/
lib.rs
benches/
fibonacci_bench.rs
fibonacci/src/lib.rs
:
pub fn fibonacci(n: u64) -> u64 {
if n < 2 {
return n;
}
let mut n1: u64 = 0;
let mut n2: u64 = 1;
for _ in 1..n {
let sum = n1 + n2;
n1 = n2;
n2 = sum;
}
n2
}
fibonacci/benches/fibonacci_bench.rs
:
#![feature(test)]
extern crate test;
extern crate fibonacci;
use test::Bencher;
#[bench]
fn bench_fibonacci(b: &mut Bencher) {
b.iter(|| fibonacci::fibonacci(40));
}
To build the benchmark test, add a rust_benchmark
target:
fibonacci/BUILD
:
package(default_visibility = ["//visibility:public"])
load("@rules_rust//rust:defs.bzl", "rust_library", "rust_benchmark")
rust_library(
name = "fibonacci",
srcs = ["src/lib.rs"],
)
rust_benchmark(
name = "fibonacci_bench",
srcs = ["benches/fibonacci_bench.rs"],
deps = [":fibonacci"],
)
Run the benchmark test using: bazel run //fibonacci:fibonacci_bench
.
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_binary
Builds a Rust binary crate.
Example:
Suppose you have the following directory structure for a Rust project with a
library crate, hello_lib
, and a binary crate, hello_world
that uses the
hello_lib
library:
[workspace]/
WORKSPACE
hello_lib/
BUILD
src/
lib.rs
hello_world/
BUILD
src/
main.rs
hello_lib/src/lib.rs
:
pub struct Greeter {
greeting: String,
}
impl Greeter {
pub fn new(greeting: &str) -> Greeter {
Greeter { greeting: greeting.to_string(), }
}
pub fn greet(&self, thing: &str) {
println!("{} {}", &self.greeting, thing);
}
}
hello_lib/BUILD
:
package(default_visibility = ["//visibility:public"])
load("@rules_rust//rust:rust.bzl", "rust_library")
rust_library(
name = "hello_lib",
srcs = ["src/lib.rs"],
)
hello_world/src/main.rs
:
extern crate hello_lib;
fn main() {
let hello = hello_lib::Greeter::new("Hello");
hello.greet("world");
}
hello_world/BUILD
:
load("@rules_rust//rust:rust.bzl", "rust_binary")
rust_binary(
name = "hello_world",
srcs = ["src/main.rs"],
deps = ["//hello_lib"],
)
Build and run hello_world
:
$ bazel run //hello_world
INFO: Found 1 target...
Target //examples/rust/hello_world:hello_world up-to-date:
bazel-bin/examples/rust/hello_world/hello_world
INFO: Elapsed time: 1.308s, Critical Path: 1.22s
INFO: Running command line: bazel-bin/examples/rust/hello_world/hello_world
Hello world
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
crate_type
Crate type that will be passed to rustc
to be used for building this crate.
This option is a temporary workaround and should be used only when building for WebAssembly targets (//rust/platform:wasi and //rust/platform:wasm).
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
linker_script
Link script to forward into linker via rustc options.
out_binary
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_library
Builds a Rust library crate.
Example:
Suppose you have the following directory structure for a simple Rust library crate:
[workspace]/
WORKSPACE
hello_lib/
BUILD
src/
greeter.rs
lib.rs
hello_lib/src/greeter.rs
:
pub struct Greeter {
greeting: String,
}
impl Greeter {
pub fn new(greeting: &str) -> Greeter {
Greeter { greeting: greeting.to_string(), }
}
pub fn greet(&self, thing: &str) {
println!("{} {}", &self.greeting, thing);
}
}
hello_lib/src/lib.rs
:
pub mod greeter;
hello_lib/BUILD
:
package(default_visibility = ["//visibility:public"])
load("@rules_rust//rust:rust.bzl", "rust_library")
rust_library(
name = "hello_lib",
srcs = [
"src/greeter.rs",
"src/lib.rs",
],
)
Build the library:
$ bazel build //hello_lib
INFO: Found 1 target...
Target //examples/rust/hello_lib:hello_lib up-to-date:
bazel-bin/examples/rust/hello_lib/libhello_lib.rlib
INFO: Elapsed time: 1.245s, Critical Path: 1.01s
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_proc_macro
Builds a Rust proc-macro crate.
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_shared_library
Builds a Rust shared library.
This shared library will contain all transitively reachable crates and native objects. It is meant to be used when producing an artifact that is then consumed by some other build system (for example to produce a shared library that Python program links against).
This rule provides CcInfo, so it can be used everywhere Bazel expects rules_cc
.
When building the whole binary in Bazel, use rust_library
instead.
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_static_library
Builds a Rust static library.
This static library will contain all transitively reachable crates and native objects. It is meant to be used when producing an artifact that is then consumed by some other build system (for example to produce an archive that Python program links against).
This rule provides CcInfo, so it can be used everywhere Bazel expects rules_cc
.
When building the whole binary in Bazel, use rust_library
instead.
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
rust_test
Builds a Rust test crate.
Examples:
Suppose you have the following directory structure for a Rust library crate with unit test code in the library sources:
[workspace]/
WORKSPACE
hello_lib/
BUILD
src/
lib.rs
hello_lib/src/lib.rs
:
pub struct Greeter {
greeting: String,
}
impl Greeter {
pub fn new(greeting: &str) -> Greeter {
Greeter { greeting: greeting.to_string(), }
}
pub fn greet(&self, thing: &str) {
println!("{} {}", &self.greeting, thing);
}
}
#[cfg(test)]
mod test {
use super::Greeter;
#[test]
fn test_greeting() {
let hello = Greeter::new("Hi");
assert_eq!("Hi Rust", hello.greet("Rust"));
}
}
To build and run the tests, simply add a rust_test
rule with no srcs
and only depends on the hello_lib
rust_library
target:
hello_lib/BUILD
:
package(default_visibility = ["//visibility:public"])
load("@rules_rust//rust:defs.bzl", "rust_library", "rust_test")
rust_library(
name = "hello_lib",
srcs = ["src/lib.rs"],
)
rust_test(
name = "hello_lib_test",
deps = [":hello_lib"],
)
Run the test with bazel build //hello_lib:hello_lib_test
.
To run a crate or lib with the #[cfg(test)]
configuration, handling inline tests, you should specify the crate directly like so.
rust_test(
name = "hello_lib_test",
crate = ":hello_lib",
# You may add other deps that are specific to the test configuration
deps = ["//some/dev/dep"],
)
Example: test
directory
Integration tests that live in the tests
directory, they are essentially built as separate crates. Suppose you have the following directory structure where greeting.rs
is an integration test for the hello_lib
library crate:
[workspace]/
WORKSPACE
hello_lib/
BUILD
src/
lib.rs
tests/
greeting.rs
hello_lib/tests/greeting.rs
:
extern crate hello_lib;
use hello_lib;
#[test]
fn test_greeting() {
let hello = greeter::Greeter::new("Hello");
assert_eq!("Hello world", hello.greeting("world"));
}
To build the greeting.rs
integration test, simply add a rust_test
target
with greeting.rs
in srcs
and a dependency on the hello_lib
target:
hello_lib/BUILD
:
package(default_visibility = ["//visibility:public"])
load("@rules_rust//rust:defs.bzl", "rust_library", "rust_test")
rust_library(
name = "hello_lib",
srcs = ["src/lib.rs"],
)
rust_test(
name = "greeting_test",
srcs = ["tests/greeting.rs"],
deps = [":hello_lib"],
)
Run the test with bazel build //hello_lib:hello_lib_test
.
name
A unique name for this target.
aliases
Remap crates to a new name or moniker for linkage to this target
These are other rust_library
targets and will be presented as the new name given.
compile_data
List of files used by this rule at compile time.
This attribute can be used to specify any data files that are embedded into
the library, such as via the
include_str!
macro.
crate
Target inline tests declared in the given crate
These tests are typically those that would be held out under
#[cfg(test)]
declarations.
crate_features
List of features to enable for this crate.
Features are defined in the code using the #[cfg(feature = "foo")]
configuration option. The features listed here will be passed to rustc
with --cfg feature="${feature_name}"
flags.
crate_name
Crate name to use for this target.
This must be a valid Rust identifier, i.e. it may contain only alphanumeric characters and underscores. Defaults to the target name, with any hyphens replaced by underscores.
crate_root
The file that will be passed to rustc
to be used for building this crate.
If crate_root
is not set, then this rule will look for a lib.rs
file (or main.rs
for rust_binary)
or the single file in srcs
if srcs
contains only one file.
data
List of files used by this rule at compile time and runtime.
If including data at compile time with include_str!() and similar,
prefer compile_data
over data
, to prevent the data also being included
in the runfiles.
deps
List of other libraries to be linked to this library target.
These can be either other rust_library
targets or cc_library
targets if
linking a native library.
edition
The rust edition to use for this crate. Defaults to the edition specified in the rust_toolchain.
env
Specifies additional environment variables to set when the test is executed by bazel test.
Values are subject to $(execpath)
and
"Make variable" substitution.
out_dir_tar
Deprecated, do not use, see [#cargo_build_script] instead.
proc_macro_deps
List of rust_library
targets with kind proc-macro
used to help build this library target.
rustc_env
Dictionary of additional "key": "value"
environment variables to set for rustc.
rust_test()/rust_binary() rules can use $(rootpath //package:target) to pass in the location of a generated file or external tool. Cargo build scripts that wish to expand locations should use cargo_build_script()'s build_script_env argument instead, as build scripts are run in a different environment - see cargo_build_script()'s documentation for more.
rustc_env_files
Files containing additional environment variables to set for rustc.
These files should contain a single variable per line, of format
NAME=value
, and newlines may be included in a value by ending a
line with a trailing back-slash (\
).
The order that these files will be processed is unspecified, so multiple definitions of a particular variable are discouraged.
rustc_flags
List of compiler flags passed to rustc
.
srcs
List of Rust .rs
source files used to build the library.
If srcs
contains more than one file, then there must be a file either
named lib.rs
. Otherwise, crate_root
must be set to the source file that
is the root of the crate to be passed to rustc to build this crate.
version
A version to inject in the cargo environment variable.
Macros and Functions
rust_test_suite
A rule for creating a test suite for a set of rust_test
targets.
This rule can be used for setting up typical rust integration tests. Given the following directory structure:
[crate]/
BUILD.bazel
src/
lib.rs
main.rs
tests/
integrated_test_a.rs
integrated_test_b.rs
integrated_test_c.rs
patterns/
fibonacci_test.rs
The rule can be used to generate rust_test targets for each source file under tests
and a test_suite which encapsulates all tests.
load("//rust:defs.bzl", "rust_binary", "rust_library", "rust_test_suite")
rust_library(
name = "math_lib",
srcs = ["src/lib.rs"],
)
rust_binary(
name = "math_bin",
srcs = ["src/main.rs"],
)
rust_test_suite(
name = "integrated_tests_suite",
srcs = glob(["tests/**"]),
deps = [":math_lib"],
)
name
The name of the test_suite
.
srcs
All test sources, typically glob(["tests/**/*.rs"])
.
kwargs
Additional keyword arguments for the underyling rust_test targets. The
tags
argument is also passed to the generated test_suite
target.