CargoMetadata doesn't work when udeps is building code about cargo-udeps HOT 7 OPEN

@jvimal-eg have you got my reply? Cargo udeps needs to be able to be called with the metadata subcommand. I'm just not sure how to implement this nicely.

from cargo-udeps.

I think it's because the cargo-udeps binary acts as cargo binary, and when the build.rs script tries to run cargo metadata, it invokes cargo-udeps with the metadata subcommand, which it doesn't recognize I think? Not sure.

from cargo-udeps.

@est31 Here's a minimal reproducible example. It might be an issue with the build_info crate I am using, but not sure at the moment. The stack trace is originating at the build_info_build::build_script(); function call in build.rs.

/bin/ls
Cargo.lock	Cargo.toml	lib

cat Cargo.toml
[workspace]
members = ["lib"]

cat lib/Cargo.toml
[package]
name = "lib"
version = "0.1.0"
authors = ["xx"]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
build-info = "0.0.23"

[build-dependencies]
build-info-build = "0.0.23"

cat lib/build.rs
fn main() {
    build_info_build::build_script();
}

cat lib/src/lib.rs
build_info::build_info!(pub fn version);

from cargo-udeps.

@est31 were you able to find out why this is happening? I tried to look into the code, but couldn't figure this out.

from cargo-udeps.

I confirm I have the same issue when having cbindgen::generate(&crate_dir).unwrap(); in my build.rs

from cargo-udeps.

@jvimal-eg have you got my reply? Cargo udeps needs to be able to be called with the metadata subcommand. I'm just not sure how to implement this nicely.

@est31 so basically cargo udeps is unusable for crates with build.rs, right?
I guess it would be easy to just run cargo metadata if cargo udeps metadata is being run, what's unnice about that solution? Sorry, don't know much about the internals of cargo udeps.

from cargo-udeps.

cargo udeps is unusable for crates with build.rs, right?

It depends on what the build.rs tries to do. If it calls cargo metadata, it might cause issues, yes.

from cargo-udeps.