Alex
That could be really helpful!
Also things like [that](https://github.com/rust-lang/cc-rs/blob/main/src/lib.rs#L1295) is not work for target with custom names, definitely. Imagine I'll name my target `arch-foo-bar-like-msvc` or more funny `same-but-not-msvc` :))) , or better for realistic example...
I did some research and experiments and here are my thoughts on the topic. `Build::target`: - sorry, currently totally incompatible with name of user's custom target, that is just file-stem...
Firstly I filled proposal-issue rust-lang/cargo/issues 14208. You could thumb-up it and comment with your suggestions, could be great 😊
I think I understood something. Perhaps we have enough information for a complete configuration of a third-party compiler. We don't need CPU because we have to use minimal-basic-cpu as the...
Well, I'll try to implement some part of it, but I need to make target field optional.
As an first ugly hot-fix I could suggest something like following. Instead of [that](https://github.com/cuviper/autocfg/blob/master/src/lib.rs#L163) `let target = env::var_os("TARGET");` do following: ```rust let target = env::var_os("AUTOCONF_TARGET").or_else(|| env::var_os("TARGET"))?; ``` So we can...
I agree, but this issue is about more than just build-std, you know. It's about "respect and use `CARGO_CFG_TARGET_...` and try to configure compiler similarly to requested target as possible...
I've did some research and realized that it's impossible to guess where spec-file is in most cases, as well as some other necessary info. So I filled proposal-issue [rust-lang/cargo/issues 14208](https://github.com/rust-lang/cargo/issues/14208).