Tests involving `cdylib` fail when cross-compiling to musl - not enough binary artifacts

[Shnatsel]

Steps to reproduce:

rustup target add x86_64-unknown-linux-musl
AUDITABLE_TEST_TARGET=x86_64-unknown-linux-musl cargo test --all-features

The test test_cargo_auditable_workspaces fails:

---- test_cargo_auditable_workspaces stdout ----
Test fixture binary map: {"binary_and_cdylib_crate": ["/home/shnatsel/Code/cargo-auditable/cargo-auditable/tests/fixtures/workspace/target/x86_64-unknown-linux-musl/debug/binary_and_cdylib_crate"], "crate_with_features": ["/home/shnatsel/Code/cargo-auditable/cargo-auditable/tests/fixtures/workspace/target/x86_64-unknown-linux-musl/debug/crate_with_features_bin"]}
/home/shnatsel/Code/cargo-auditable/cargo-auditable/tests/fixtures/workspace/target/x86_64-unknown-linux-musl/debug/binary_and_cdylib_crate dependency info: VersionInfo { packages: [Package { name: "binary_and_cdylib_crate", version: Version { major: 0, minor: 1, patch: 0 }, source: "local", kind: Runtime, dependencies: [1], features: [] }, Package { name: "library_crate", version: Version { major: 0, minor: 1, patch: 0 }, source: "local", kind: Runtime, dependencies: [], features: [] }] }
thread 'test_cargo_auditable_workspaces' panicked at 'assertion failed: crate_with_features_bins.len() == 2', cargo-auditable/tests/it.rs:149:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[tofay]

cdylib's aren't produced by default with musl targets - rust-lang/rust#59302. I think for now we should update the tests to not look for cdylibs on musl - I can do that this weekend.

[Shnatsel]

Hmm, apparently RUSTFLAGS="-C target-feature=-crt-static" is needed to produce a cdylib. It's mentioned in the issue you linked, but rust-lang/cargo#8607 spells it out explicitly.

I'll go ahead and update the tests now that I understand what to change. Thanks!