View on GitHub

Clang Power Tools

Bringing clang-tidy magic to Visual Studio C++ developers

Version History

Clang Power Tools 3.3.1

April 24, 2018

Bugs:

Clang Power Tools 3.3

March 29, 2018

Improvements:

Clang Power Tools 3.2.1

March 23, 2018

Bugs:

Clang Power Tools 3.2

March 22, 2018

Improvements:

Bugs:

Clang Power Tools 3.1

March 12, 2018

Improvements:

Bugs:

Clang Power Tools 3.0.1

March 2nd, 2018

Bugs:

Clang Power Tools 3.0

March 1st, 2018

NEW: Built-in support for clang-format
Auto-format source file on save, configurable style options, file extension rules, etc.

Improvements:

Bugs:

Clang Power Tools 2.8

February 20, 2018

Improvements:

Bugs:

Clang Power Tools 2.7

February 8, 2018

Improvements:

Bugs:

Clang Power Tools 2.6

January 29, 2018

Until now, we’ve used the %INCLUDE% environment variable for setting clang include directories. That was equivalent to using -isystem for each directory.

Unfortunately, this caused headers included relative to those include directories to be ignored when running compiling/tidying because they were treated as system headers.

Having this brought to our attention, going forward we will use -I and -isystem to pass include directories to clang, with the following defaults:

Q: What does this mean?
A: You’ll most likely see new warnings when compiling or tidying your code-base.

Q: Will my build fail?
A: Only if you have specified -Werror (treat warnings as errors).

Q: What should I do?
A: - Make sure to include third party library dependencies via the Include directories project option. Additional include directories should point only to code you can modernize.
- Resolve remaining warnings related to your code.

Q: Can I use ClangPowerTools using the old behavior?
A: Yes. We’ve added, for compatibility reasons, a UI option that allows clang to treat additional includes as system headers. Keep in mind this means we will potentially miss some of your headers when calling clang.

You may want to use this option if using -Werror (treating warnings as errors) until you’ve reorganized your includes, since any new warnings will break your build.

Q: What about the continuous integration script (clang-build.ps1)?
A: You can specify the -treat-sai switch and it will have the old behavior.

Improvements:

Bugs:

Clang Power Tools 2.5.1

January 17, 2018

Bugs:

Clang Power Tools 2.5

January 12, 2018

Improvements:

Bugs:

Clang Power Tools 2.4.1

December 28, 2017

Bugs:

Clang Power Tools 2.4

December 21, 2017

Improvements:

Bugs:

Clang Power Tools 2.3

December 13, 2017

Improvements:

Bugs:

Clang Power Tools 2.2

December 11, 2017

Bugs:

Clang Power Tools 2.1

December 7, 2017

Improvements:

Bugs:

Clang Power Tools 2.0

November 26, 2017

Improvements:

Clang Power Tools 1.7.1

November 20, 2017

Bugs:

Clang Power Tools 1.7

November 16, 2017

Improvements:

Bugs:

Clang Power Tools 1.6

November 9, 2017

Improvements:

Bugs:

Clang Power Tools 1.5.1

November 3rd, 2017

Improvements:

Bugs:

Clang Power Tools 1.5

November 1st, 2017

Improvements:

Clang Power Tools 1.4

October 27, 2017

Improvements:

Bugs:

Clang Power Tools 1.3.1

October 23, 2017

Bugs:

Clang Power Tools 1.3

October 19, 2017

Improvements:

Bugs:

Clang Power Tools 1.2

October 13, 2017

Improvements:

Bugs:

Clang Power Tools 1.1

October 8, 2017

Improvements:

Bugs:

Clang Power Tools 1.0.1

September 30, 2017

Improvements:

Bugs:

Clang Power Tools 1.0

September 27, 2017

First official release.