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

74 lines
2.1 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)
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
SOURCES += \
clangstaticanalyzerconfigwidget.cpp \
clangstaticanalyzerdiagnosticview.cpp \
Allow users to suppress diagnostics. This patch deals with what is likely the most common use case: Filtering specific messages at a particular location. The current granularity is essentially per-file (and per-function, where possible), which seems more useful than taking line numbers into account, as that would not be robust with regards to code changes elsewhere in the file. We can fine-tune this if the need arises. Change-Id: I4e9b2671fa199339cc3b995953d072b840cd3205 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-19 18:08:38 +01:00
clangstaticanalyzerprojectsettings.cpp \
clangstaticanalyzerprojectsettingsmanager.cpp \
clangstaticanalyzerprojectsettingswidget.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
clangstaticanalyzerruncontrol.cpp \
clangstaticanalyzerrunner.cpp \
clangstaticanalyzertool.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
clangtidyclazyruncontrol.cpp \
clangtidyclazyrunner.cpp \
clangtidyclazytool.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 \
clangtoolssettings.cpp \
clangtoolsutils.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 += \
clangstaticanalyzerconfigwidget.h \
clangstaticanalyzerdiagnosticview.h \
Allow users to suppress diagnostics. This patch deals with what is likely the most common use case: Filtering specific messages at a particular location. The current granularity is essentially per-file (and per-function, where possible), which seems more useful than taking line numbers into account, as that would not be robust with regards to code changes elsewhere in the file. We can fine-tune this if the need arises. Change-Id: I4e9b2671fa199339cc3b995953d072b840cd3205 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-19 18:08:38 +01:00
clangstaticanalyzerprojectsettings.h \
clangstaticanalyzerprojectsettingsmanager.h \
clangstaticanalyzerprojectsettingswidget.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
clangstaticanalyzerruncontrol.h \
clangstaticanalyzerrunner.h \
clangstaticanalyzertool.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
clangtidyclazyruncontrol.h \
clangtidyclazyrunner.h \
clangtidyclazytool.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 \
clangtoolssettings.h \
clangtoolsutils.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 += \
Allow users to suppress diagnostics. This patch deals with what is likely the most common use case: Filtering specific messages at a particular location. The current granularity is essentially per-file (and per-function, where possible), which seems more useful than taking line numbers into account, as that would not be robust with regards to code changes elsewhere in the file. We can fine-tune this if the need arises. Change-Id: I4e9b2671fa199339cc3b995953d072b840cd3205 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-19 18:08:38 +01:00
clangstaticanalyzerconfigwidget.ui \
clangstaticanalyzerprojectsettingswidget.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 += \
clangstaticanalyzerpreconfiguredsessiontests.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 += \
clangstaticanalyzerpreconfiguredsessiontests.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