I actually have a crate that contains a dependent crate as sub-folder. While the parent crate requires a
./.cargo/config.toml file to successfully compile the crate in the subfolder should be build without thus settings. According to the documentation cargo will merge config files if they exist along the search path. However, I'd like to skip the usage of the parent folder cargo config file usage.
In fact the thing is that the parent cargo config file contains a specific build target, but the dependent crate in the subfolder (it's a proc-macro crate) need always to be build for the host system.
Any way to stop cargo from looking in the parent folder if a config file is found in the current folder already or just prevent cargo from looking for a config file at all?
Thanks in advance for any hint.