~~1. when you try compile your project with cargo build,
then your build.rs generates a binary by rust compiler, and that is called by cargo package manager,
but cargo itself already has a lock on some files located at ~/.cargo/registry/ (may),
so vergen calls cargo metadata --format-version 1 to get the metadata for the crate.
This is never done. This process can never end, because at the moment the down-stream project's compile command (such ascargo build) is waiting for the build script to finish, and vergen is waiting for the cargo build to release the file lock.~~
It's probably very rare, and now it's suddenly works again, so leave it as an FYI, vergen calls the cargo command internally anyway... I personally don't think this is a good design
~~1. when you try compile your project with
cargo build
,build.rs
generates a binary by rust compiler, and that is called by cargo package manager,~/.cargo/registry/
(may),cargo metadata --format-version 1
to get the metadata for the crate.cargo build
) is waiting for the build script to finish, and vergen is waiting for the cargo build to release the file lock.~~~~# what happen? see following screenshots:~~