intractabilis

> we're not able to take advantage of modern CMake functionality because we need to support older platforms You should check your answers against simple, verifiable facts. Google Benchmark's `CMakeLists.txt`...

> So once it does, let's cycle back to the google benchmark side of the problem. This is a strategy that will not help anybody. Changing GTest first will break...

> i'm open to ideas but i'm a bit stumped. Remove setting the standard altogether. This is usually used for programs that use new features, not vice versa, requesting everyone...

I apologize for being a bad communicator. Why don't you want to just remove `add_cxx_compiler_flag(-std=c++11) `? I am not sure what problem the author of that line was trying to...

> my first patch on the linked PR did exactly that (just removed the flag) but that ends up with compilers falling back to older standards by default To C++03?

> so unless you like breakage, > you need to specificly ask for that specific version when compiling If you want new features, yes. You shouldn't downgrade the compiler. C++...

@dominichamon If some compilers we support fall back to C++03, we should check in CMake for that compilers specifically and set C++14 for them. If they don't support C++14, we...

`CXX_STANDARD` is just a compiler-independent way to specify `-std=c++XX`, no more, no less. I'll comment on the rest later.

Another issue with having the build output in "output" is that the errors are not clickable.

I understand that this is not for everyone, but I switched to Meson plus xPack (https://marketplace.visualstudio.com/items?itemName=ilg-vscode.xpack). I never regretted this choice. I have color output for builds and hyperlinked error...