6 releases
0.2.5 | Dec 21, 2023 |
---|---|
0.2.4 | Dec 21, 2023 |
0.1.0 | May 7, 2023 |
#225 in Cargo plugins
12KB
196 lines
Exporting cargo compiler artifacts (tests, benches)
Motivation
It's quite challenging to export secondary artifacts like tests and benchmark executables. Those kind of artifacts can be very valuable for different reasons:
- packing test executables in the contaier to run them later on a different platform
- comparing and analyzing assembly of performance benchmarks
For final artifacts we have target/(release|debug)/{crate-name}
, but test and benchmark executables are containing
hash like target/release/deps/app-25de5d28a523d3c2
. Moreover it changes every time compiler options are changed. For
this reason methods like find
and cp
doesn't work well for extracting such artifacts.
Thankfully, compiler provide service messages (cargo build --message-format=json
) which allows to list all the
artifacts generated by the compiler.
Installing
$ cargo install cargo-export
Using
-
export all test binaries to
target/tests
directory$ cargo export target/tests -- test
Under the hood this command will run
cargo test --no-run --message-format=json
and copy all the generated binaries in thetarget/tests
directory. -
export all benchmark binaries to
target/bench
directory$ cargo export target/bench -- bench
-
export all benchmark binaries to
target/bench
directory and add postfix-main
to each executable$ cargo export target/bench -t main -- bench
-
build and export benchmarks with a specific feature
$ cargo export target/bench -- bench --feature=my-feature
-
build and export benchmarks using nightly
$ cargo +nightly export target/bench -- bench
Dependencies
~1.8–3MB
~55K SLoC