maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/cmake/modules/ClangConfig.cmake.in

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

22 lines
743 B
CMake
Raw Normal View History

Make it easier to build against a pre-built Clang package with CMake Installing <prefix>/share/clang/cmake/ClangConfig.cmake makes CMake's builtin find_package() utility work with Clang. This also allows downstream consumers of Clang to statically link against libraries like clangAST and have that pull in dependencies like clangBasic and LLVMSupport. See the CMake docs on packages: http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html llvm-svn: 221411
2014-11-06 07:14:59 +08:00
# This file allows users to call find_package(Clang) and pick up our targets.
[ClangConfig] Instead of hard coding the ClangTargets location to /ClangTargets.cmake, follow LLVM's example and use a pre-computed cmake variable @CLANG_CONFIG_EXPORTS_FILE@. This just makes ClangConfig more consistent with LLVMConfig. llvm-svn: 274178
2016-06-30 05:59:19 +08:00
@CLANG_CONFIG_CODE@
[cmake] Hint find_package() to prefer LLVM installed alongside clang Include a path hint for find_package() in ClangConfig.cmake to ensure that CMake prefers LLVM installed alongside clang over the default search path. If two versions of LLVM are installed in the system, and one of them is in PATH, CMake's find_package() magic prefers the CMake directory alongside that install by default. Adding a relative hint makes it possible to prioritize to the install from which find_package() is called. If you want to build e.g. LLDB against another install of LLVM, you can pass LLVM_CONFIG override. In this case, LLDB queries the prefix from llvm-config and uses the CMake files located there. However, when including ClangConfig, the implicit find_package() nevertheless prefers PATH-found LLVM over the one used previously by LLDB, and two versions of LLVMConfig end up being loaded. This could be fixed on LLDB end up by explicitly forcing custom package search location. However, it seems simpler and safer to add a hint to ClangConfig than to track every usage of ClangConfig. Differential Revision: https://reviews.llvm.org/D29304 llvm-svn: 293632
2017-01-31 22:15:40 +08:00
find_package(LLVM REQUIRED CONFIG
HINTS "@CLANG_CONFIG_LLVM_CMAKE_DIR@")
[ClangConfig] Store all of the targets exported in the variable CLANG_EXPORTED_TARGETS. llvm-svn: 274180
2016-06-30 05:59:23 +08:00
set(CLANG_EXPORTED_TARGETS "@CLANG_EXPORTS@")
[ClangConfig] Instead of hard coding the ClangTargets location to /ClangTargets.cmake, follow LLVM's example and use a pre-computed cmake variable @CLANG_CONFIG_EXPORTS_FILE@. This just makes ClangConfig more consistent with LLVMConfig. llvm-svn: 274178
2016-06-30 05:59:19 +08:00
set(CLANG_CMAKE_DIR "@CLANG_CONFIG_CMAKE_DIR@")
[CMake] Add CLANG_INCLUDE_DIRS to CMake exports This patch adds setting CLANG_INCLUDE_DIRS in the generated CMake package configuration files. llvm-svn: 294207
2017-02-07 02:17:23 +08:00
set(CLANG_INCLUDE_DIRS "@CLANG_CONFIG_INCLUDE_DIRS@")
Make it possible for client code to consume CLANG_LINK_CLANG_DYLIB If a client code wants to consume clang libraries, it needs to know CLANG_LINK_CLANG_DYLIB value in order to decide whether to use the DYLIB or individual components. Differential Revision: https://reviews.llvm.org/D82291
2020-06-30 20:11:28 +08:00
set(CLANG_LINK_CLANG_DYLIB "@CLANG_LINK_CLANG_DYLIB@")
[ClangConfig] Instead of hard coding the ClangTargets location to /ClangTargets.cmake, follow LLVM's example and use a pre-computed cmake variable @CLANG_CONFIG_EXPORTS_FILE@. This just makes ClangConfig more consistent with LLVMConfig. llvm-svn: 274178
2016-06-30 05:59:19 +08:00
Make it easier to build against a pre-built Clang package with CMake Installing <prefix>/share/clang/cmake/ClangConfig.cmake makes CMake's builtin find_package() utility work with Clang. This also allows downstream consumers of Clang to statically link against libraries like clangAST and have that pull in dependencies like clangBasic and LLVMSupport. See the CMake docs on packages: http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html llvm-svn: 221411
2014-11-06 07:14:59 +08:00
# Provide all our library targets to users.
[cmake] Add support for multiple distributions LLVM's build system contains support for configuring a distribution, but it can often be useful to be able to configure multiple distributions (e.g. if you want separate distributions for the tools and the libraries). Add this support to the build system, along with documentation and usage examples. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D89177
2020-10-02 05:35:28 +08:00
@CLANG_CONFIG_INCLUDE_EXPORTS@
[CMake] NFC. Add clang-tablegen-targets utility target By creating this target other projects that depend on clang-generated headers (like LLDB) will no longer be order-dependent on Clang being processed by CMake first. Also, by creating a dummy of this target in ClangConfig.cmake, projects that can build against out-of-tree clang can freely depend on the target without needing to have conditionals for if clang is in-tree or out-of-tree. llvm-svn: 309390
2017-07-28 23:33:47 +08:00
# By creating clang-tablegen-targets here, subprojects that depend on Clang's
# tablegen-generated headers can always depend on this target whether building
# in-tree with Clang or not.
if(NOT TARGET clang-tablegen-targets)
add_custom_target(clang-tablegen-targets)
endif()