Sean Leather

This is how one test for the target and host `x86_64-unknown-linux-gnu` fails on Azure Pipelines: ``` test gnu_i686 ... cargo:warning=clang: error: no such file or directory: 'foo.c' cargo:warning=clang: error: no...

What's the best way to fix the tests? It's not clear to me why the host and target are both set to the same or even why the host is...

Okay, I have better understanding of the test infrastructure. Ignore my musings above. I'm currently performing some renovations to the tests.

I was actually thinking of doing something to follow symlinks, too, after working on #407. But I'd really be fine with just following symlinks instead of #407. I think it's...

Just to open up the discussion a bit more to alternatives for compiler detection, we could instead use a small C program with `#ifdef`s to identify the compiler. Here's a...

But, as I just realized, my suggestion in https://github.com/alexcrichton/cc-rs/issues/408#issuecomment-498548064 won't work for cross-compiling. So it looks like the current executable-name-based mechanism with symlink resolution is good enough.

> While you're right that the executable strategy doesn't work for cross compilation it would work for using the preprocessor to learn what the compiler is It wouldn't work if...

> But I believe you're suggesting a way to use the preprocessor alone – without building an executable – to determine the compiler? Ah, I see this is already implemented...

Just to provide an update, I'm actively working on a solution to this. I should hopefully have something to show within the next few days. The hard part is done....

I don't have an answer, but I just wanted to put this thought out there. Currently, `cmake-rs` does this: * if `opt-level ≡ 0` then `CMAKE_BUILD_TYPE=Debug`, * if `opt-level ∈...