Marshall Clow wrote:
I have this in in user-config.jam:
using darwin : 11 : "/Sources/gcc/gcc-4.8.2/bin/bin/g++" : <cxxflags>"-std=c++11" ;
And I just use: b2 toolset=darwin-11
This works, but it's not as convenient as having a separate gcc11 toolset. Currently, toolset=gcc finds whatever g++ there is in the PATH, and automatically detects its version, so for instance, if I have g++ 4.5.3, it puts the compiler output into a gcc-4.5.3 directory, and if I then run b2 with g++ 4.8.1 in the PATH, it can see that the previous test run is not the same, so it re-runs the tests, putting the result into a gcc-4.8.1 directory. Which is exactly what I want. Ideally, the C++11 mode tests would go into gcc11-(detected version), for the same reason. A similar problem occurs when I need to run several test runs using different #defines, but that's probably harder to solve. Ideally, if I define=THIS and define=THAT, the output should probably go into a define-a6d9ba0c subdirectory (similar to how threading=multi goes into threading-multi/.)