feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity
Files
92bb42dd36394162a9badecf029234e1c343b5a7
qt-creator/src/plugins/clangtools/clangtools.pro

86 lines
2.2 KiB
Prolog
Raw Normal View History

Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
include(../../qtcreatorplugin.pri)
ClangTools: Add tool that runs clang-tidy and clazy ... over the whole project. Generate and read serialized files to get diagnostics. Change-Id: Iafc25fc70443107a040a995efc038aed35102bbf Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-01-17 15:08:30 +01:00
include(../../shared/clang/clang_installation.pri)
ClangTools: Remove clang executable settings We use custom clang executable and it does not make sense anymore to give a choice of changing it. Change-Id: Icf86042ac3fcd08c320ef2bbdaabef1102b023b5 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-30 15:26:36 +02:00
include(../../shared/clang/clang_defines.pri)
Clang: Do not try to build ClangTools without LLVM Change-Id: Iecec62047b5f2327be6843ac9d3ccd87be4bf8f6 Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2018-04-26 15:56:04 +02:00
requires(!isEmpty(LLVM_VERSION))
ClangTools: Add tool that runs clang-tidy and clazy ... over the whole project. Generate and read serialized files to get diagnostics. Change-Id: Iafc25fc70443107a040a995efc038aed35102bbf Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-01-17 15:08:30 +01:00
LIBS += $$LIBCLANG_LIBS
INCLUDEPATH += $$LLVM_INCLUDEPATH
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
Import YAML-Parser yaml-cpp Version: tags/yaml-cpp-0.6.2 License: MIT yaml-cpp requires c++11 and since yaml-cpp 0.6 there is no dependency on boost anymore. A YAML parser is needed for the ClangTools plugin to parse exported diagnostics from clang-tidy/clazy: $ clang-tidy -export-fixes=/tmp/tidy.yaml source.cpp The imported source is stripped of unneeded files as documented with src/libs/3rdparty/yaml-cpp/patches/0001-yaml-cpp-Strip-unneeded-sources.patch (generated with "git format-patch -D") Change-Id: Ib0a521b5aff4b1cd058eb480bfb99fde4b320dc7 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2019-07-30 15:26:31 +02:00
include(../../shared/yaml-cpp/yaml-cpp_installation.pri)
ClangTools: Support loading exported diagnostics Add a new toolbar button to load diagnostics exported with $ clang-tidy -export-fixes=/path/to/file $ clazy-standalone -export-fixes=/path/to/file (master version) Change-Id: I8316fe0706a18222e68220ef4fbfdc7ae8d09804 Reviewed-by: David Schulz <david.schulz@qt.io>
2019-07-23 08:28:13 +02:00
isEmpty(EXTERNAL_YAML_CPP_FOUND) {
DEFINES += YAML_CPP_DLL
} else {
Import YAML-Parser yaml-cpp Version: tags/yaml-cpp-0.6.2 License: MIT yaml-cpp requires c++11 and since yaml-cpp 0.6 there is no dependency on boost anymore. A YAML parser is needed for the ClangTools plugin to parse exported diagnostics from clang-tidy/clazy: $ clang-tidy -export-fixes=/tmp/tidy.yaml source.cpp The imported source is stripped of unneeded files as documented with src/libs/3rdparty/yaml-cpp/patches/0001-yaml-cpp-Strip-unneeded-sources.patch (generated with "git format-patch -D") Change-Id: Ib0a521b5aff4b1cd058eb480bfb99fde4b320dc7 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2019-07-30 15:26:31 +02:00
LIBS += $$EXTERNAL_YAML_CPP_LIBS
QMAKE_CXXFLAGS += $$EXTERNAL_YAML_CPP_CXXFLAGS
}
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
SOURCES += \
ClangTools: Fix applying fixits one by one If a file had multiple fixits and only a subset was applied, the remaining fixits in that file were invalidated. Fix this by adjusting the locations of the not yet applied fixits. Change-Id: I2c190412e871e9011c4d4a62ed938e76ad4cdf72 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-24 09:03:44 +02:00
clangfixitsrefactoringchanges.cpp \
ClangTools: Prompt for files to analyze If the run button is clicked, the user is prompted to select the files for analysis. Change-Id: I21e4ee6b7c14392a8c1a901ac7aa1c9c16e30f0d Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-02 14:51:05 +02:00
clangselectablefilesdialog.cpp \
ClangTools: Rename some classes and files ...to some more generic names since they are not anymore specific to the clang static analyzer. * ClangStaticAnalyzerDiagnosticView --> DiagnosticView * ClangStaticAnalyzerDiagnosticFilterModel --> DiagnosticFilterModel * ClangStaticAnalyzerPreconfiguredSesssionTest --> PreconfiguredSessionTests * clangstaticanalyzerprojectsettingswidget.* --> clangtoolsdiagnosticwidget.* Change-Id: Ifd34f207d31dc24d6a97654aca76ff27b5025547 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-08 17:33:29 +02:00
clangtoolsdiagnosticview.cpp \
clangtoolsprojectsettingswidget.cpp \
ClangTools: Add tool that runs clang-tidy and clazy ... over the whole project. Generate and read serialized files to get diagnostics. Change-Id: Iafc25fc70443107a040a995efc038aed35102bbf Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-01-17 15:08:30 +01:00
clangtidyclazyrunner.cpp \
ClangTools: Split generic part from static analyzer tool To reuse it for other clang-based tools. Change-Id: I6c0d8e9eee543fa08faf3bf93c9fac33e43c6820 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2018-01-17 15:08:30 +01:00
clangtool.cpp \
clangtoolruncontrol.cpp \
clangtoolrunner.cpp \
clangtoolsdiagnostic.cpp \
clangtoolsdiagnosticmodel.cpp \
clangtoolslogfilereader.cpp \
clangtoolsplugin.cpp \
ClangTools: Remember selected files Change-Id: I53227d0ada37b613b7312149bb8e7c15f6bf2bcc Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-07 17:04:26 +02:00
clangtoolsprojectsettings.cpp \
ClangTools: Split generic part from static analyzer tool To reuse it for other clang-based tools. Change-Id: I6c0d8e9eee543fa08faf3bf93c9fac33e43c6820 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2018-01-17 15:08:30 +01:00
clangtoolssettings.cpp \
ClangTools: Rename configuration widget This configuration is used not only for static analyzer but for all tools. Change-Id: I5ef282500e0addb4ca104b34530e56fba80f59b8 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-30 16:07:59 +02:00
clangtoolsutils.cpp \
ClangTools: Query the tools for supported checks ...instead of hardcoding them for a particular version of clang-tidy/clazy. While at it, move also the tidy/clazy widgets to ClangTools as this simplifies feeding data to them. Reduce also the built-in configs to a single one using clang-tidy's and clazy's default checks as they look very reasonable and saves us some porting effort. Also, our previous built-in configs were just too numerous. Change-Id: Ib9297acb7810a940b86a23a8695530506a570394 Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2019-10-21 14:59:57 +02:00
diagnosticconfigswidget.cpp \
executableinfo.cpp \
ClangTools: Move run settings to projects mode Make the global run settings available per project in project mode and thus remove the diagnostic config selection from the selectable-files-dialog: * Extract the classes RunSettings and RunSettingsWidget instead of duplicating stuff. * Ensure to pick up the old settings * Add some convenience buttons/links in projects mode allowing to restore the global settings, to open the global settings and to navigate (back) to the analyzer mode. Change-Id: I1b91b6f8e58a87a025774e4643c46e176b2a8885 Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-09-13 10:49:14 +02:00
runsettingswidget.cpp \
ClangTools: Rename ClangToolsConfigWidget -> SettingsWidget Change-Id: I37ee3435054b27fd9e990f2923e6246ecb9e631f Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-08-27 16:09:39 +02:00
settingswidget.cpp \
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
HEADERS += \
ClangTools: Prompt for files to analyze If the run button is clicked, the user is prompted to select the files for analysis. Change-Id: I21e4ee6b7c14392a8c1a901ac7aa1c9c16e30f0d Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-02 14:51:05 +02:00
clangfileinfo.h \
ClangTools: Fix applying fixits one by one If a file had multiple fixits and only a subset was applied, the remaining fixits in that file were invalidated. Fix this by adjusting the locations of the not yet applied fixits. Change-Id: I2c190412e871e9011c4d4a62ed938e76ad4cdf72 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-24 09:03:44 +02:00
clangfixitsrefactoringchanges.h \
ClangTools: Prompt for files to analyze If the run button is clicked, the user is prompted to select the files for analysis. Change-Id: I21e4ee6b7c14392a8c1a901ac7aa1c9c16e30f0d Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-02 14:51:05 +02:00
clangselectablefilesdialog.h \
ClangTools: Rename some classes and files ...to some more generic names since they are not anymore specific to the clang static analyzer. * ClangStaticAnalyzerDiagnosticView --> DiagnosticView * ClangStaticAnalyzerDiagnosticFilterModel --> DiagnosticFilterModel * ClangStaticAnalyzerPreconfiguredSesssionTest --> PreconfiguredSessionTests * clangstaticanalyzerprojectsettingswidget.* --> clangtoolsdiagnosticwidget.* Change-Id: Ifd34f207d31dc24d6a97654aca76ff27b5025547 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-08 17:33:29 +02:00
clangtoolsdiagnosticview.h \
clangtoolsprojectsettingswidget.h \
ClangTools: Add tool that runs clang-tidy and clazy ... over the whole project. Generate and read serialized files to get diagnostics. Change-Id: Iafc25fc70443107a040a995efc038aed35102bbf Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-01-17 15:08:30 +01:00
clangtidyclazyrunner.h \
ClangTools: Split generic part from static analyzer tool To reuse it for other clang-based tools. Change-Id: I6c0d8e9eee543fa08faf3bf93c9fac33e43c6820 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2018-01-17 15:08:30 +01:00
clangtool.h \
clangtoolruncontrol.h \
clangtoolrunner.h \
clangtools_global.h \
clangtoolsconstants.h \
clangtoolsdiagnostic.h \
clangtoolsdiagnosticmodel.h \
clangtoolslogfilereader.h \
clangtoolsplugin.h \
ClangTools: Remember selected files Change-Id: I53227d0ada37b613b7312149bb8e7c15f6bf2bcc Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-07 17:04:26 +02:00
clangtoolsprojectsettings.h \
ClangTools: Split generic part from static analyzer tool To reuse it for other clang-based tools. Change-Id: I6c0d8e9eee543fa08faf3bf93c9fac33e43c6820 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2018-01-17 15:08:30 +01:00
clangtoolssettings.h \
ClangTools: Rename configuration widget This configuration is used not only for static analyzer but for all tools. Change-Id: I5ef282500e0addb4ca104b34530e56fba80f59b8 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-30 16:07:59 +02:00
clangtoolsutils.h \
ClangTools: Query the tools for supported checks ...instead of hardcoding them for a particular version of clang-tidy/clazy. While at it, move also the tidy/clazy widgets to ClangTools as this simplifies feeding data to them. Reduce also the built-in configs to a single one using clang-tidy's and clazy's default checks as they look very reasonable and saves us some porting effort. Also, our previous built-in configs were just too numerous. Change-Id: Ib9297acb7810a940b86a23a8695530506a570394 Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2019-10-21 14:59:57 +02:00
diagnosticconfigswidget.h \
executableinfo.h \
ClangTools: Move run settings to projects mode Make the global run settings available per project in project mode and thus remove the diagnostic config selection from the selectable-files-dialog: * Extract the classes RunSettings and RunSettingsWidget instead of duplicating stuff. * Ensure to pick up the old settings * Add some convenience buttons/links in projects mode allowing to restore the global settings, to open the global settings and to navigate (back) to the analyzer mode. Change-Id: I1b91b6f8e58a87a025774e4643c46e176b2a8885 Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-09-13 10:49:14 +02:00
runsettingswidget.h \
ClangTools: Rename ClangToolsConfigWidget -> SettingsWidget Change-Id: I37ee3435054b27fd9e990f2923e6246ecb9e631f Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-08-27 16:09:39 +02:00
settingswidget.h \
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
FORMS += \
ClangTools: Add missing ui file to pro file Change-Id: I0c63048795f641f06b3212716fb93f9fc2c7bcc9 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2019-09-13 08:16:52 +02:00
clangselectablefilesdialog.ui \
ClangTools: Rename some classes and files ...to some more generic names since they are not anymore specific to the clang static analyzer. * ClangStaticAnalyzerDiagnosticView --> DiagnosticView * ClangStaticAnalyzerDiagnosticFilterModel --> DiagnosticFilterModel * ClangStaticAnalyzerPreconfiguredSesssionTest --> PreconfiguredSessionTests * clangstaticanalyzerprojectsettingswidget.* --> clangtoolsdiagnosticwidget.* Change-Id: Ifd34f207d31dc24d6a97654aca76ff27b5025547 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-08 17:33:29 +02:00
clangtoolsprojectsettingswidget.ui \
ClangTools: Query the tools for supported checks ...instead of hardcoding them for a particular version of clang-tidy/clazy. While at it, move also the tidy/clazy widgets to ClangTools as this simplifies feeding data to them. Reduce also the built-in configs to a single one using clang-tidy's and clazy's default checks as they look very reasonable and saves us some porting effort. Also, our previous built-in configs were just too numerous. Change-Id: Ib9297acb7810a940b86a23a8695530506a570394 Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2019-10-21 14:59:57 +02:00
clazychecks.ui \
ClangTools: Move run settings to projects mode Make the global run settings available per project in project mode and thus remove the diagnostic config selection from the selectable-files-dialog: * Extract the classes RunSettings and RunSettingsWidget instead of duplicating stuff. * Ensure to pick up the old settings * Add some convenience buttons/links in projects mode allowing to restore the global settings, to open the global settings and to navigate (back) to the analyzer mode. Change-Id: I1b91b6f8e58a87a025774e4643c46e176b2a8885 Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-09-13 10:49:14 +02:00
runsettingswidget.ui \
ClangTools: Rename ClangToolsConfigWidget -> SettingsWidget Change-Id: I37ee3435054b27fd9e990f2923e6246ecb9e631f Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-08-27 16:09:39 +02:00
settingswidget.ui \
ClangTools: Query the tools for supported checks ...instead of hardcoding them for a particular version of clang-tidy/clazy. While at it, move also the tidy/clazy widgets to ClangTools as this simplifies feeding data to them. Reduce also the built-in configs to a single one using clang-tidy's and clazy's default checks as they look very reasonable and saves us some porting effort. Also, our previous built-in configs were just too numerous. Change-Id: Ib9297acb7810a940b86a23a8695530506a570394 Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2019-10-21 14:59:57 +02:00
tidychecks.ui \
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
Add unit tests. These test the complete workflow as the user experiences it when clicking "Start". Intended usage: (1) Run sdktool to set up a kit with the toolchain you want to test against (using a temporary directory). The tests assume exactly one Kit to be present. (2) Start Creator with a matching settings path and "-load ClangStaticAnalyzer -test ClangStaticAnalyzer". (3) Repeat until all toolchains have been tested. The initial implementation tests one trivial source file with both qbs and qmake. Change-Id: I810f23e2990a789a4dd9f1dd16335fbcf5c5f39f Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-04 15:19:30 +01:00
equals(TEST, 1) {
ClangStaticAnalyzer: Simplify testing various kits The already available ClangStaticAnalyzerUnitTests uses the automatically set up "Desktop" kit to run the analyzer. This is fine for tests that are run in the build environment of Qt Creator. However, testing different kits on the same machine means to build Qt Creator itself with those kits, which is not practical. The new ClangStaticAnalyzerSessionTests will open the predefined session "ClangStaticAnalyzerPreconfiguredSession" and for each project and each target it will run the analyzer. If there is no such session, the test will be skipped. To manually preconfigure the desired session: 1. ./qtcreator -settingspath /custom/path 2. Set up the desired kits. 3. Create a session with the name ClangStaticAnalyzerPreconfiguredSession and load the desired test projects. To run the test: ./qtcreator -settingspath /custom/path -test ClangStaticAnalyzer,testPreconfiguredSession Change-Id: I0f027353854088d3acf8acecc16c74e9f0516e7d Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
2016-07-08 12:07:53 +02:00
HEADERS += \
ClangTools: Rename some classes and files ...to some more generic names since they are not anymore specific to the clang static analyzer. * ClangStaticAnalyzerDiagnosticView --> DiagnosticView * ClangStaticAnalyzerDiagnosticFilterModel --> DiagnosticFilterModel * ClangStaticAnalyzerPreconfiguredSesssionTest --> PreconfiguredSessionTests * clangstaticanalyzerprojectsettingswidget.* --> clangtoolsdiagnosticwidget.* Change-Id: Ifd34f207d31dc24d6a97654aca76ff27b5025547 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-08 17:33:29 +02:00
clangtoolspreconfiguredsessiontests.h \
ClangTools: Generalize unit tests Add an option to run different tools. Change-Id: Iaf5c928663a888526eba9ee9d1fcea59e6083488 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-24 15:30:19 +02:00
clangtoolsunittests.h
ClangStaticAnalyzer: Simplify testing various kits The already available ClangStaticAnalyzerUnitTests uses the automatically set up "Desktop" kit to run the analyzer. This is fine for tests that are run in the build environment of Qt Creator. However, testing different kits on the same machine means to build Qt Creator itself with those kits, which is not practical. The new ClangStaticAnalyzerSessionTests will open the predefined session "ClangStaticAnalyzerPreconfiguredSession" and for each project and each target it will run the analyzer. If there is no such session, the test will be skipped. To manually preconfigure the desired session: 1. ./qtcreator -settingspath /custom/path 2. Set up the desired kits. 3. Create a session with the name ClangStaticAnalyzerPreconfiguredSession and load the desired test projects. To run the test: ./qtcreator -settingspath /custom/path -test ClangStaticAnalyzer,testPreconfiguredSession Change-Id: I0f027353854088d3acf8acecc16c74e9f0516e7d Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
2016-07-08 12:07:53 +02:00
SOURCES += \
ClangTools: Rename some classes and files ...to some more generic names since they are not anymore specific to the clang static analyzer. * ClangStaticAnalyzerDiagnosticView --> DiagnosticView * ClangStaticAnalyzerDiagnosticFilterModel --> DiagnosticFilterModel * ClangStaticAnalyzerPreconfiguredSesssionTest --> PreconfiguredSessionTests * clangstaticanalyzerprojectsettingswidget.* --> clangtoolsdiagnosticwidget.* Change-Id: Ifd34f207d31dc24d6a97654aca76ff27b5025547 Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
2018-05-08 17:33:29 +02:00
clangtoolspreconfiguredsessiontests.cpp \
ClangTools: Generalize unit tests Add an option to run different tools. Change-Id: Iaf5c928663a888526eba9ee9d1fcea59e6083488 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-24 15:30:19 +02:00
clangtoolsunittests.cpp
ClangStaticAnalyzer: Simplify testing various kits The already available ClangStaticAnalyzerUnitTests uses the automatically set up "Desktop" kit to run the analyzer. This is fine for tests that are run in the build environment of Qt Creator. However, testing different kits on the same machine means to build Qt Creator itself with those kits, which is not practical. The new ClangStaticAnalyzerSessionTests will open the predefined session "ClangStaticAnalyzerPreconfiguredSession" and for each project and each target it will run the analyzer. If there is no such session, the test will be skipped. To manually preconfigure the desired session: 1. ./qtcreator -settingspath /custom/path 2. Set up the desired kits. 3. Create a session with the name ClangStaticAnalyzerPreconfiguredSession and load the desired test projects. To run the test: ./qtcreator -settingspath /custom/path -test ClangStaticAnalyzer,testPreconfiguredSession Change-Id: I0f027353854088d3acf8acecc16c74e9f0516e7d Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
2016-07-08 12:07:53 +02:00
ClangTools: Generalize unit tests Add an option to run different tools. Change-Id: Iaf5c928663a888526eba9ee9d1fcea59e6083488 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2018-04-24 15:30:19 +02:00
RESOURCES += clangtoolsunittests.qrc
Add unit tests. These test the complete workflow as the user experiences it when clicking "Start". Intended usage: (1) Run sdktool to set up a kit with the toolchain you want to test against (using a temporary directory). The tests assume exactly one Kit to be present. (2) Start Creator with a matching settings path and "-load ClangStaticAnalyzer -test ClangStaticAnalyzer". (3) Repeat until all toolchains have been tested. The initial implementation tests one trivial source file with both qbs and qmake. Change-Id: I810f23e2990a789a4dd9f1dd16335fbcf5c5f39f Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-04 15:19:30 +01:00
}
Import Clang Static Analyzer plugin 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>
2014-09-25 11:11:58 +02:00
DISTFILES += \
ClangStaticAnalyzer: Make the *.qdoc easily accessible Change-Id: I9ab2a3b19fcfe4b3554057a0f8f441db17681eb2 Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>
2016-01-20 19:06:49 +01:00
tests/tests.pri \
$${IDE_SOURCE_TREE}/doc/src/analyze/creator-clang-static-analyzer.qdoc
Copy Permalink