.cargo/config in root makes writing utilities more frustrating
Crzyrndm opened this issue · comments
cargo traverses parent directories until it fins a .cargo/config and then applies that at any level.
Because of this, there is no way to write tooling for the current PC that doesn't require --target=... which is somewhat frustrating when that's what you're trying to do...
Ran into this trying to write a script to generate the macros for #277. A build script would avoid the issue but this would be a constant file (not requiring compile time generation) and would add a lot of noise if any other features were to be added (as I understand it, build scripts are single file).
use build script or a different crate