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

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 lines
287 B
CMake
Raw Normal View History

[ms-inline asm] Add various MC components to clang build to support MS-style inline assembly. llvm-svn: 161594
2012-08-10 01:17:01 +08:00
set(LLVM_LINK_COMPONENTS
[CMake] Update target_link_libraries() and LLVM_LINK_COMPONENTS for each CMakeLists.txt. llvm-svn: 196916
2013-12-10 20:40:37 +08:00
Support
Add libsupport to list of libraries to link into diagtool llvm-svn: 137110
2011-08-09 11:41:03 +08:00
)
[diagtool] Install diagtool when LLVM_INSTALL_TOOLCHAIN_ONLY is ON. Not sure about other platforms but `install-xcode-toolchain` was already including diagtool in the toolchain. This change makes it possible to install diagtool during Apple's 2-stage build. Instead of dropping `if (NOT LLVM_INSTALL_TOOLCHAIN_ONLY)` conditional I've switched to `add_clang_tool` which handles install targets. Also a few other clang tools like clang-format, clang-scan-deps are using this macro, so it is good to be consistent. rdar://problem/15386909 Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D80770
2020-05-29 08:06:33 +08:00
add_clang_tool(diagtool
Add 'diagtool' to the 'tools/' directory. diagtool is a new tool (WIP) for analyzing and working with clang diagnostics. Some interesting stats from 'diagtool list-warnings' on the current version of clang: Percentage of warnings with flags: 48.79% Number of unique flags: 148 Average number of diagnostics per flag: 2.041 llvm-svn: 137109
2011-08-09 11:39:19 +08:00
diagtool_main.cpp
DiagTool.cpp
[diagtool] Re-add show-enabled, minimizing the code pulled in from Frontend. Now correctly builds with both GNU make and CMake. llvm-svn: 157932
2012-06-05 00:57:50 +08:00
DiagnosticNames.cpp
[diagtool] Add a 'find-diagnostic-id' subcommand that converts a name of the diagnostic to its enum value This will be used by a script that invokes clang in a debugger and forces it to stop when it reports a particular diagnostic. Differential Revision: https://reviews.llvm.org/D35306 llvm-svn: 307813
2017-07-13 00:41:49 +08:00
FindDiagnosticID.cpp
Add 'diagtool' to the 'tools/' directory. diagtool is a new tool (WIP) for analyzing and working with clang diagnostics. Some interesting stats from 'diagtool list-warnings' on the current version of clang: Percentage of warnings with flags: 48.79% Number of unique flags: 148 Average number of diagnostics per flag: 2.041 llvm-svn: 137109
2011-08-09 11:39:19 +08:00
ListWarnings.cpp
[diagtool] Re-add show-enabled, minimizing the code pulled in from Frontend. Now correctly builds with both GNU make and CMake. llvm-svn: 157932
2012-06-05 00:57:50 +08:00
ShowEnabledWarnings.cpp
[diagtool] Add a new "tree" command to shows warnings activated by a flag. % diagtool tree -Wunused-value -Wunused-value -Wunused-comparison warn_unused_comparison -Wunused-result warn_unused_result warn_unused_call warn_unused_container_subscript_expr warn_unused_expr warn_unused_property_expr warn_unused_voidptr llvm-svn: 159093
2012-06-24 08:07:45 +08:00
TreeView.cpp
Add 'diagtool' to the 'tools/' directory. diagtool is a new tool (WIP) for analyzing and working with clang diagnostics. Some interesting stats from 'diagtool list-warnings' on the current version of clang: Percentage of warnings with flags: 48.79% Number of unique flags: 148 Average number of diagnostics per flag: 2.041 llvm-svn: 137109
2011-08-09 11:39:19 +08:00
)
cmake: Add CLANG_LINK_CLANG_DYLIB option Summary: Setting CLANG_LINK_CLANG_DYLIB=ON causes clang tools to link against libclang_shared.so instead of the individual component libraries. Reviewers: mgorny, beanz, smeenai, phosek, sylvestre.ledru Subscribers: arphaman, cfe-commits, llvm-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D63503 llvm-svn: 365092
2019-07-04 06:45:55 +08:00
clang_target_link_libraries(diagtool
[CMake] Use PRIVATE in target_link_libraries for executables We currently use target_link_libraries without an explicit scope specifier (INTERFACE, PRIVATE or PUBLIC) when linking executables. Dependencies added in this way apply to both the target and its dependencies, i.e. they become part of the executable's link interface and are transitive. Transitive dependencies generally don't make sense for executables, since you wouldn't normally be linking against an executable. This also causes issues for generating install export files when using LLVM_DISTRIBUTION_COMPONENTS. For example, clang has a lot of LLVM library dependencies, which are currently added as interface dependencies. If clang is in the distribution components but the LLVM libraries it depends on aren't (which is a perfectly legitimate use case if the LLVM libraries are being built static and there are therefore no run-time dependencies on them), CMake will complain about the LLVM libraries not being in export set when attempting to generate the install export file for clang. This is reasonable behavior on CMake's part, and the right thing is for LLVM's build system to explicitly use PRIVATE dependencies for executables. Unfortunately, CMake doesn't allow you to mix and match the keyword and non-keyword target_link_libraries signatures for a single target; i.e., if a single call to target_link_libraries for a particular target uses one of the INTERFACE, PRIVATE, or PUBLIC keywords, all other calls must also be updated to use those keywords. This means we must do this change in a single shot. I also fully expect to have missed some instances; I tested by enabling all the projects in the monorepo (except dragonegg), and configuring both with and without shared libraries, on both Darwin and Linux, but I'm planning to rely on the buildbots for other configurations (since it should be pretty easy to fix those). Even after this change, we still have a lot of target_link_libraries calls that don't specify a scope keyword, mostly for shared libraries. I'm thinking about addressing those in a follow-up, but that's a separate change IMO. Differential Revision: https://reviews.llvm.org/D40823 llvm-svn: 319840
2017-12-06 05:49:56 +08:00
PRIVATE
Remove a goofy CMake hack and use the standard CMake facilities to express library-level dependencies within Clang. This is no more verbose really, and plays nicer with the rest of the CMake facilities. It should also have no change in functionality. llvm-svn: 158888
2012-06-21 09:30:21 +08:00
clangBasic
clangFrontend
)