It will be part of the installation from 3.5 on.
Also look explicitly for "clang-cl" on Windows now, as we do not
ship clang.exe.
Change-Id: I67e22ed4251791dd59015dd6f9648c7a14d941d7
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
Without this patch, validation kicks in only on user input.
Change-Id: I791c45b214e7e171f59c66c7d96f3e85a668427e
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
Use aggregation instead of inheritance for customization of validation
Change-Id: I5a9703bad5bace78e8c3cc1e2c353a734001bd0a
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
Also warn the user in the settings page against this.
Change-Id: I4dbae953aa85f8dbdc9baa8dd0fda8ff0da45b76
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
This plugin adds "Clang Static Analyzer" to the Analyze mode, which
processes all implementation/source project files of the current
project. For this, it will call the clang executable for each file.
The found diagnostics will be displayed in a view similar to the one
used in "Valgrind Memory Analyzer".
The user can specify the clang executable to use and the number of
concurrent processes to launch in Menu: Tools > Options > Analyzer >
Clang Static Analyzer.
Main TODOs:
* Fiddle around the appropriate command line options, currently only
defines and include paths are passed on.
* Tests on Windows / OS X.
* Remove dependency to clangcodemodel by moving the functions that
create command line arguments to CppTools. Mostly they are not even
specific to clang (but would also work with gcc).
* Maybe limit to a range of tested clang versions.
* How to deal with directory containing all the log files after the
user starts a new run or Creator is shut down? (delete it? leave it
there? make it configurable?).
* Find out how to properly integrate the tests.
Imaginable future additions:
* Adding a button to load result/log files from a directory, e.g. if
the user used the 'scan-build' approach.
* Adding a button with a filter menu in order to display only
diagnostics from certain categories, similar to "Valgrind Memory
Analyzer".
Change-Id: I6aeb5dfdbdfa239a06c03dd8759a983df71b77ea
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>