llvm-project/llvm/lib/FileCheck/CMakeLists.txt

add_llvm_component_library(LLVMFileCheck
  FileCheck.cpp

  ADDITIONAL_HEADER_DIRS
  "${LLVM_MAIN_INCLUDE_DIR}/llvm/FileCheck"
)

target_link_libraries(LLVMFileCheck LLVMSupport)
Reland [FileCheck] Move FileCheck implementation out of LLVMSupport into its own library This relands e9a3d1a401b07cbf7b11695637f1b549782a26cd which was originally missing linking LLVMSupport into LLMVFileCheck which broke the SHARED_LIBS build. Original summary: The actual FileCheck logic seems to be implemented in LLVMSupport. I don't see a good reason for having FileCheck implemented there as it has a very specific use while LLVMSupport is a dependency of pretty much every LLVM tool there is. In fact, the only use of FileCheck I could find (outside the FileCheck tool and the FileCheck unit test) is a single call in GISelMITest.h. This moves the FileCheck logic to its own LLVMFileCheck library. This way only FileCheck and the GlobalISelTests now have a dependency on this code. Reviewed By: jhenderson Differential Revision: https://reviews.llvm.org/D86344 2020-09-01 19:21:18 +08:00			`add_llvm_component_library(LLVMFileCheck`
			`FileCheck.cpp`

			`ADDITIONAL_HEADER_DIRS`
			`"${LLVM_MAIN_INCLUDE_DIR}/llvm/FileCheck"`
[build] normalize components dependencies Use LINK_COMPONENTS instead of explicit target_link_libraries for components. This avoids redundancy and potential inconsistencies. Differential Revision: https://reviews.llvm.org/D91461 2020-11-14 05:45:55 +08:00			`)`
Revert "[build] normalize components dependencies" This reverts commit c6ef6e1690d517b3401ea06b1fe46871eb67434d. Basically, publicly linked libraries have a different semantic than components, which link libraries privately. Differential Revision: https://reviews.llvm.org/D91461 2020-11-19 02:19:36 +08:00
			`target_link_libraries(LLVMFileCheck LLVMSupport)`