Cannot run Mutants on complex build setup

[elizabethshirley]

I'm working with a codebase that has both a binary and a library, the binary is for an embedded device and the library can be run on embedded device and on the host computer. The library itself is unit tested using
cargo test --target x86_64-unknown-linux-gnu
Unfortunately it seems that mutants tries to build the entire binary instead of just going after the library, this causes mutants to fail because crate test is not available for the embedded device.

Is there a way to configure mutants so it will only go after the tests in the library?

[sourcefrog]

If the binary and library are in different packages you should be able to run cargo mutants -p whateverlib?

If they're in the same package then it might be more complicated.

mutants.out/debug.log will show what command it's running, I guess something like cargo test --no-run --verbose [email protected]. Does this fail in your package, on the host?

If the binary fails to build on the host and you want it in the same package then perhaps you could use https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-required-features-field so that the binary can be turned on only on places where it will work?

[elizabethshirley]

What I ultimately needed to do was completely detangle the testable part into a separate workspace with guards for the different builds (no_std vs std)

Thanks for the help :)