This PR enables the selection of clang-tidy as a code analyser when the code analyser action of Visual Studio is run in the IDE. Further details can be found in the official documentation.
How does this PR change Premake's behavior?
Add configuration-scoped option clangtidy for Visual Studio 2019 and above.
I have tried to follow pre-existing conventions:
The option name was a lowercase boolean based on compilebuildoutputs as an example.
The test_output_props tests for vs2019 were based on vs2022 test_output_props.
A test was also added to ensure pre-vs2019 configs were not affected.
Documentation was added based on the buildstlmodules example, which was a similar boolean.
Did you check all the boxes?
[x] Focus on a single fix or feature; remove any unrelated formatting or code changes
[x] Add unit tests showing fix or feature works; all tests pass
[ ] Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
What does this PR do?
This PR enables the selection of clang-tidy as a code analyser when the code analyser action of Visual Studio is run in the IDE. Further details can be found in the official documentation.
How does this PR change Premake's behavior?
Add configuration-scoped option
clangtidyfor Visual Studio 2019 and above.I have tried to follow pre-existing conventions:
compilebuildoutputsas an example.buildstlmodulesexample, which was a similar boolean.Did you check all the boxes?
[x] Focus on a single fix or feature; remove any unrelated formatting or code changes
[x] Add unit tests showing fix or feature works; all tests pass
[ ] Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
[x] Follow our coding conventions
[x] Minimize the number of commits
[x] Align documentation to your changes