The paths to the compiler and to the python executable may need to
be quoted (if they're installed into e.g. "C:\Program Files").
All testing commands that are executed expect a gcc compatible command
line interface, while clang-cl uses different command line options.
In the original testing config, if the chosen compiler was clang-cl, it
was replaced with clang++ by looking for such an executable in the path.
For the new from-scratch test configs, I instead chose to add
"--driver-mode=g++" to flags - invoking "clang-cl --driver-mode=g++"
has the same effect as invoking "clang++", without needing to run any
heuristics for picking a different compiler executable.
This requires including %{{flags}} in the _supportsVerify function,
as running plain %{{cxx} on its own won't work that way. Alternatively,
the --driver-mode option could be appended on the %{cxx} substitution
(but it's not straightforward to change substitutions that already are
defined).
There's a weird character here.