Vladimir Prus wrote:
But what then would be your recommendation? How can I have a working setup, in which I can issue
b2 toolset=gcc,gcc-cxx11,gcc-cxx14,clang,clang-cxx11,clang-cxx14,msvc-8.0,msvc-12.0
and have it properly detect that gcc by default doesn't support C++11, but does in -std=c++11 mode?
I think it's impossible to do right now, and the easiest way to support it is to make configure.build function take an additional list of properties that are relevant for this particular test, so that you can pass toolset-gcc:std in your configuration check.
Interestingly though, -cxx11 and -cxx14 do end up encoded in the directory names (or running tests with the above command wouldn't work.) So it seems that the directory logic and the caching logic are separate and the former seems more useful, at least in my specific case.