maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang-tools-extra/unittests/clang-tidy/CMakeLists.txt

27 lines
550 B
CMake
Raw Normal View History

Initial architecture for clang-tidy. This is the first version of a possible clang-tidy architecture. The purpose of clang-tidy is to detect errors in adhering to common coding patterns, e.g. described in the LLVM Coding Standards. This is still heavily in flux. Review: http://llvm-reviews.chandlerc.com/D884 llvm-svn: 187345
2013-07-29 16:19:24 +08:00
set(LLVM_LINK_COMPONENTS
support
)
get_filename_component(CLANG_LINT_SOURCE_DIR
${CMAKE_CURRENT_SOURCE_DIR}/../../clang-tidy REALPATH)
include_directories(${CLANG_LINT_SOURCE_DIR})
add_extra_unittest(ClangTidyTests
Output clang-tidy errors in a consistent order. Summary: Sort errors by path, file offset and message. Reviewers: djasper, klimek Reviewed By: djasper CC: cfe-commits Differential Revision: http://reviews.llvm.org/D3314 llvm-svn: 205759
2014-04-08 20:27:49 +08:00
ClangTidyDiagnosticConsumerTest.cpp
Add clang-tidy -line-filter option to filter findings by line ranges. Summary: This is going to be used for a clang-tidy-diff script to display warnings in changed lines only. The option uses JSON, as its value is not intended to be entered manually. Reviewers: klimek Reviewed By: klimek Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D3873 llvm-svn: 209450
2014-05-23 00:07:11 +08:00
ClangTidyOptionsTest.cpp
Initial architecture for clang-tidy. This is the first version of a possible clang-tidy architecture. The purpose of clang-tidy is to detect errors in adhering to common coding patterns, e.g. described in the LLVM Coding Standards. This is still heavily in flux. Review: http://llvm-reviews.chandlerc.com/D884 llvm-svn: 187345
2013-07-29 16:19:24 +08:00
LLVMModuleTest.cpp
Add an argument comment checker to clang-tidy. This checks that parameters named in comments that appear before arguments in function and constructor calls match the parameter name used in the callee's declaration. For example: void f(int x, int y); void g() { f(/*y=*/0, /*z=*/0); } contains two violations of the policy, as the names 'x' and 'y' used in the declaration do not match names 'y' and 'z' used at the call site. I think there is significant value in being able to check/enforce this policy as a way of guarding against accidental API misuse and silent breakages caused by API changes. Although this pattern appears somewhat frequently in the LLVM codebase, this policy is not prescribed by the LLVM coding standards at the moment, so it lives under 'misc'. Differential Revision: http://llvm-reviews.chandlerc.com/D2914 llvm-svn: 204113
2014-03-18 12:46:45 +08:00
GoogleModuleTest.cpp
MiscModuleTest.cpp)
Initial architecture for clang-tidy. This is the first version of a possible clang-tidy architecture. The purpose of clang-tidy is to detect errors in adhering to common coding patterns, e.g. described in the LLVM Coding Standards. This is still heavily in flux. Review: http://llvm-reviews.chandlerc.com/D884 llvm-svn: 187345
2013-07-29 16:19:24 +08:00
target_link_libraries(ClangTidyTests
[CMake] clang-tools-extra: Update dependencies. llvm-svn: 196860
2013-12-10 09:41:10 +08:00
clangAST
clangASTMatchers
clangBasic
clangFrontend
Initial architecture for clang-tidy. This is the first version of a possible clang-tidy architecture. The purpose of clang-tidy is to detect errors in adhering to common coding patterns, e.g. described in the LLVM Coding Standards. This is still heavily in flux. Review: http://llvm-reviews.chandlerc.com/D884 llvm-svn: 187345
2013-07-29 16:19:24 +08:00
clangTidy
Fix clang-tidy dependencies and bad file comment. This addresses comments in post-commit review of r187345. llvm-svn: 187707
2013-08-04 23:56:30 +08:00
clangTidyGoogleModule
[CMake] clang-tools-extra: Update dependencies. llvm-svn: 196860
2013-12-10 09:41:10 +08:00
clangTidyLLVMModule
Add an argument comment checker to clang-tidy. This checks that parameters named in comments that appear before arguments in function and constructor calls match the parameter name used in the callee's declaration. For example: void f(int x, int y); void g() { f(/*y=*/0, /*z=*/0); } contains two violations of the policy, as the names 'x' and 'y' used in the declaration do not match names 'y' and 'z' used at the call site. I think there is significant value in being able to check/enforce this policy as a way of guarding against accidental API misuse and silent breakages caused by API changes. Although this pattern appears somewhat frequently in the LLVM codebase, this policy is not prescribed by the LLVM coding standards at the moment, so it lives under 'misc'. Differential Revision: http://llvm-reviews.chandlerc.com/D2914 llvm-svn: 204113
2014-03-18 12:46:45 +08:00
clangTidyMiscModule
Initial architecture for clang-tidy. This is the first version of a possible clang-tidy architecture. The purpose of clang-tidy is to detect errors in adhering to common coding patterns, e.g. described in the LLVM Coding Standards. This is still heavily in flux. Review: http://llvm-reviews.chandlerc.com/D884 llvm-svn: 187345
2013-07-29 16:19:24 +08:00
clangTooling
)