[e2e tests] Add a chip-specific startup test.
This test demonstrates how to write a rust test with a controlled
component running in the RV32 cpu.
1. Declare command structures to be shared between the rust test and C
helper program.
2. Write a C helper program to read the hardware properties to be
checked by the rust test into the command/status structures.
3. Write a rust test program to read out the data and check for
expected values.
Signed-off-by: Chris Frantz <cfrantz@google.com>
diff --git a/rules/ujson.bzl b/rules/ujson.bzl
index e425024..9388765 100644
--- a/rules/ujson.bzl
+++ b/rules/ujson.bzl
@@ -19,17 +19,20 @@
rustfmt_files = ctx.attr._rustfmt.data_runfiles.files.to_list()
rustfmt = [f for f in rustfmt_files if f.basename == "rustfmt"][0]
+ defines = ["-D{}".format(d) for d in ctx.attr.defines]
+
# The pipeline for generating rust code from a ujson header file:
# 1. Preprocess the file with RUST_PREPROCESSOR_EMIT
# 2. Grep out all the preprocessor noise (which starts with `#`).
# 3. Substitute all `rust_attr` for `#`, thus creating rust attributes.
# 4. Format it with `rustfmt` so it looks nice and can be inspected.
command = """
- {preprocessor} -nostdinc -I. -DRUST_PREPROCESSOR_EMIT=1 -DNOSTDINC=1 $@ \
+ {preprocessor} -nostdinc -I. -DRUST_PREPROCESSOR_EMIT=1 -DNOSTDINC=1 {defines} $@ \
| grep -v '#' \
| sed -e "s/rust_attr/#/g" \
| {rustfmt} > {module}""".format(
preprocessor = cc_toolchain.preprocessor_executable,
+ defines = " ".join(defines),
module = module.path,
rustfmt = rustfmt.path,
)
@@ -52,6 +55,9 @@
providers = [CcInfo],
doc = "ujson cc_library targets to generate Rust for",
),
+ "defines": attr.string_list(
+ doc = "C preprocessor defines",
+ ),
"ujson_lib": attr.label(
default = "//sw/device/lib/ujson",
doc = "Location of the ujson library",
