Vladimir Prus wrote:
John Maddock wrote:
using intel-win : 8.0-vc6 : : <compatibility>vc6 ; using intel-win : 8.0-vc7 : : <compatibility>vc7 ;
And "8.0-vc6" and "8.0-vc7" will be the version in library name. If that version are equal to what autolinking wants, there should be no problem.
John runs screaming from the building......!
OK, so the same compiler could produce any one of:
"iw" "iw-8.0" "iw-8.0-vc7"
This is *impossible* to handle with auto-linking and even worse than version 1!
Both in V1 and V2, Boost.Build user can specify any name/version for a compiler, and there's no way to prevent that. In addition, I can always make replace "cl.exe" with my own program which will invoke gcc.exe ;-) The point is: build system cannot be expected to determine toolset version automatically. I think it's reasonable to ask a person building boost to provide explicit version numbers when initializing a toolset, no? (While msvc.jam has some logic to autodetect installed version from target path, this cannot be considered 100% reliable).
Some systems invoke the tools with -v to see what they tell you about the version. It would be good to have that capability, but of course first we need someone to code up the portable popen. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com