Continue the work in https://github.com/rust-lang/cc-rs/pull/1413, and avoid the pre-generated list of Clang/LLVM triples in favour of constructing it from the target information. I'd like to make sure that this list matches what `rustc`, so I'm filing PRs to make their use of LLVM triples simpler: - https://github.com/rust-lang/rust/pull/138426 - https://github.com/rust-lang/rust/pull/138427 - https://github.com/rust-lang/rust/pull/138429 - https://github.com/rust-lang/rust/pull/138431 - A PR for avoiding arch-only LLVM triples (`riscv32`) in favour of more components (`riscv32-unknown-none`) - WIP more? Alternatively, maybe use `rustc --print llvm-tuple` [if that becomes viable](https://github.com/rust-lang/compiler-team/issues/846).
Continue the work in #1413, and avoid the pre-generated list of Clang/LLVM triples in favour of constructing it from the target information.
I'd like to make sure that this list matches what
rustc, so I'm filing PRs to make their use of LLVM triples simpler:armv7-sony-vita-newlibeabihfLLVM target triple rust#138426x86_64-unknown-illumosLLVM target triple rust#138429uclibcLLVM target triples rust#138431riscv32) in favour of more components (riscv32-unknown-none)Alternatively, maybe use
rustc --print llvm-tupleif that becomes viable.