llvm-project/clang-tools-extra/tool-template/CMakeLists.txt

set(LLVM_LINK_COMPONENTS
  Support
  )

add_clang_executable(tool-template
  ToolTemplate.cpp
  )

clang_target_link_libraries(tool-template
  PRIVATE
  clangAST
  clangASTMatchers
  clangBasic
  clangFrontend
  clangTooling
  clangToolingRefactoring
  )
[CMake] clang-tools-extra: Update dependencies. llvm-svn: 196860 2013-12-10 01:41:10 +00:00			`set(LLVM_LINK_COMPONENTS`
			`Support`
			`)`

Reverted to correct commit this time. llvm-svn: 162624 2012-08-24 23:29:33 +00:00			`add_clang_executable(tool-template`
			`ToolTemplate.cpp`
			`)`

[clang-tools-extra] [cmake] Link against libclang-cpp whenever possible Use clang_target_link_libraries() in order to support linking against libclang-cpp instead of static libraries. Differential Revision: https://reviews.llvm.org/D68448 llvm-svn: 373786 2019-10-04 20:30:02 +00:00			`clang_target_link_libraries(tool-template`
[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-05 21:49:56 +00:00			`PRIVATE`
[CMake] clang-tools-extra: Update dependencies. llvm-svn: 196860 2013-12-10 01:41:10 +00:00			`clangAST`
			`clangASTMatchers`
			`clangBasic`
			`clangFrontend`
			`clangTooling`
Rename clangToolingRefactor to clangToolingRefactoring for consistency with its directory See "[cfe-dev] The name of clang/lib/Tooling/Refactoring". Differential Revision: https://reviews.llvm.org/D62420 llvm-svn: 361684 2019-05-25 00:27:19 +00:00			`clangToolingRefactoring`
[CMake] clang-tools-extra: Update dependencies. llvm-svn: 196860 2013-12-10 01:41:10 +00:00			`)`