Phil McArdle

So my original use case for this was as a result of my original workaround for [#859](https://github.com/gradle/gradle/issues/859#issue-189400974). Because I had only one `toolChain` defined at a time, and in my...

In my above comment, I suggested that I would workaround this by coercing Gradle to only configure one C++ toolchain at a time, using pre-defined / command-line project properties, but...

Okay, the above doesn't work. I have the usual issue with competing configuration being applied at different times - much of the configuration that depends on knowing which toolchain will...

Hahaha, that works 😅 I didn't need the use of NativeBinarySpecInternal, so I'd be curious to know what that would have been for. I'm able to do this across my...

Additionally, the `toolChain` changes are automatically propagated to the respective GoogleTest testSuites, though I have no idea which code is handling that I am grateful nonetheless 🙂

I didn't even realise it was internal, but I can see now that it's not on the javadoc pages (and I can see that I looked for this exact method...

I've been meaning to comment on this one, but just in case this PR is going the other way - as a user of scripted pipeline I have a need...