Open wiktorwieclaw opened 1 year ago
I've looked into the source code and the problem lies within the cargo-project
crate.
cargo-project
gets the target
directory from 3 different sources, in this specific order:
CARGO_TARGET_DIR
environment variablebuild.target-dir
property from .cargo/config.toml
One can take advantage of the 1st or 2nd step to workaround the problem.
Good catch! Can you make a PR of this here?
Oh you already did by cargo-project, nevermind! haha
I think it may be because we are using a workspace. Here is the project.
Notice that it tries to find the
target
dir incansat/crates/cansat-stm32f4/
, but it should be justcansat/
. As you can see, I'm callingcargo dfu
fromcrates/cansat-stm32f4
.It works fine on my linux machine and the path gets properly resolved to: