Currently, cargo swift enforces the target directory to be located in the crates top-level directory, which may be undesirable for crates that are part of a workspace. This behavior was introduced as a quick fix to #24.
Instead, cargo swift should locate the target directory. This is possible by invoking cargo metadata --no-deps --format-version 1
Currently, cargo swift enforces the target directory to be located in the crates top-level directory, which may be undesirable for crates that are part of a workspace. This behavior was introduced as a quick fix to #24.
Instead, cargo swift should locate the target directory. This is possible by invoking
cargo metadata --no-deps --format-version 1