Fixes #391. Visual Studio 2022 v17.10.0 introduced a new toolchain version 14.40.33807, which does not start with "14.3". This trips up the cl.exe finding logic in msvc.jam.
As discussed in #391, it is really a bad move of Microsoft to bump their toolchain version that way, but since you cannot have Visual Studio 2022 v17.9.x and v17.10.x installed side-by-side, I think it does not make much sense to introduce a msvc-14.4 toolset in b2.
Therefore, I would propose to recognize toolchain versions starting with "14.4" also as msvc-14.3, which is a relatively small change.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other (please describe):
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Proposed changes
Fixes #391. Visual Studio 2022 v17.10.0 introduced a new toolchain version 14.40.33807, which does not start with "14.3". This trips up the
cl.exefinding logic inmsvc.jam.As discussed in #391, it is really a bad move of Microsoft to bump their toolchain version that way, but since you cannot have Visual Studio 2022 v17.9.x and v17.10.x installed side-by-side, I think it does not make much sense to introduce a
msvc-14.4toolset in b2.Therefore, I would propose to recognize toolchain versions starting with "14.4" also as
msvc-14.3, which is a relatively small change.Types of changes
What types of changes does your code introduce?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.