Hi,
is it intentional that cargo install --path . re-downloads all dependencies and re-builds everything instead of relying on the build artifacts in the current package directory (e.g. output of a previous cargo build --release)?

1 post - 1 participant

Read full topic