Vladimir Prus wrote:
Assuming the concrete proposal is:
Whenever no explicit version of msvc is provided, run compiler, extract version from the output, and use that.
and I'm asked to implement that in code, it would require access to all versions of msvc for which that behaviour is desired, plus a couple of days.
Personally, I'd rather we take a few days to fix this, rather than ship "as is". Vladimir: if there's anything I can do to aid testing of any changes then let me know. I believe that if we have "using msvc ;" in user-config.jam then it automatically detects the available versions and sets the most recent as the default? Can we rig it so that --toolset=msvc has the same effect? The only issue is what happens if the user invokes bjam from within an msvc command prompt. Should we expect --toolset=msvc to invoke the compiler that's currently in the path and detect it's version correctly? My gut feeling is this may be too much to ask for, but if so we should say so in the docs (Dave?). Regards, John.