recognition of msvc toolset v143 for Visual Studio 17.10 or newer did not work
Proposed changes
Checking also for prefix 14.4
Types of changes
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.
[ ] I added myself to the copyright attributions for significant changes
[ x] I checked that tests pass locally with my changes
[ ] I added tests that prove my fix is effective or that my feature works
[ ] I added necessary documentation (if appropriate)
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
recognition of msvc toolset v143 for Visual Studio 17.10 or newer did not work
Proposed changes
Checking also for prefix 14.4
Types of changes
Put an
x
in the boxes that applyChecklist
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.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...