cargo-rtic-scope
cargo-rtic-scope copied to clipboard
build: handle .cargo/config above temporary directory?
When cargo builds something, it will traverse directories upwards and look for .cargo/config{,.toml} files. If such a file is found when the intermediate library is built, something wrong is likely to occur. Can we handle this file, or is it up to the user to ensure that the environment does not need to be modified?