search for: add_tablegen

...e > + DEPENDS CONFIGURE_LLVM_NATIVE > + WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} > + COMMENT "Building libLLVMSupport for native TableGen...") > + add_custom_target(NATIVE_LIB_LLVMSUPPORT DEPENDS LIB_LLVMSUPPORT) > +endif(LLVM_USE_HOST_TOOLS) > + > macro(add_tablegen target project) > set(${target}_OLD_LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS}) > set(LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS} TableGen) > @@ -109,7 +118,7 @@ macro(add_tablegen target project) > > add_custom_command(OUTPUT ${${project}_TABLEGEN_EXE} > COM...

...ld . --target LLVMSupport --config Release > + DEPENDS CONFIGURE_LLVM_NATIVE > + WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} > + COMMENT "Building libLLVMSupport for native TableGen...") > +add_custom_target(NATIVE_LIB_LLVMSUPPORT DEPENDS LIB_LLVMSUPPORT) > + > macro(add_tablegen target project) > set(${target}_OLD_LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS}) > set(LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS} TableGen) > @@ -109,7 +116,7 @@ macro(add_tablegen target project) > > add_custom_command(OUTPUT ${${project}_TABLEGEN_EXE} > COM...

...>> + WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} >>> + COMMENT "Building libLLVMSupport for native TableGen...") >>> + add_custom_target(NATIVE_LIB_LLVMSUPPORT DEPENDS LIB_LLVMSUPPORT) >>> +endif(LLVM_USE_HOST_TOOLS) >>> + >>> macro(add_tablegen target project) >>> set(${target}_OLD_LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS}) >>> set(LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPONENTS} TableGen) >>> @@ -109,7 +118,7 @@ macro(add_tablegen target project) >>> >>> add_custom_command(OUTPUT ${${proje...

...lso attached if that's more convenient): >> >> diff --git a/cmake/modules/TableGen.cmake b/cmake/modules/TableGen.cmake >> index 452a728..be6729d 100644 >> --- a/cmake/modules/TableGen.cmake >> +++ b/cmake/modules/TableGen.cmake >> @@ -107,9 +107,18 @@ macro(add_tablegen target project) >> endif() >> set(${project}_TABLEGEN_EXE ${${project}_TABLEGEN_EXE} PARENT_SCOPE) >> >> + if(NOT TARGET NATIVE_LIB_LLVMSUPPORT) Instead of doing this you could move creating this out of the macro. Then it will be executed when the file is in...

...t, got something thrown together. Here it is inline (also attached if that's more convenient): diff --git a/cmake/modules/TableGen.cmake b/cmake/modules/TableGen.cmake index 452a728..be6729d 100644 --- a/cmake/modules/TableGen.cmake +++ b/cmake/modules/TableGen.cmake @@ -107,9 +107,18 @@ macro(add_tablegen target project) endif() set(${project}_TABLEGEN_EXE ${${project}_TABLEGEN_EXE} PARENT_SCOPE) + if(NOT TARGET NATIVE_LIB_LLVMSUPPORT) + add_custom_command(OUTPUT LIB_LLVMSUPPORT + COMMAND ${CMAKE_COMMAND} --build . --target LLVMSupport --config Release +...

Hi Brad, I have a few questions regarding ExternalProject_Add. For me it doesn't really work as expected. I add the following code to the tools/clang/runtime/CMakeLists.txt to configure compiler-rt as external project: ExternalProject_Add(compiler-rt #DEPENDS clang clang++ llvm-config PREFIX ${CMAKE_BINARY_DIR}/projects/compiler-rt SOURCE_DIR ${COMPILER_RT_SRC_ROOT}

Hello backend devs, Been working on a parallelization bug in the cmake configs, where parallel makefile builds of llvm with clang and native tablegen would usually break during linking in either either the clang_tblgen or llvm_tblgen targets. Looking at the cmake command that generates the tablegen makefile commands (I think) (cmake/modules/TableGen.cmake:113-117):

Hi folks, Building any LLVM project currently requires invoking CMake inside <monorepo-root>/llvm, while setting the projects to enable in the LLVM_ENABLE_PROJECTS variable. This has the downside that CMake processing for the LLVM subproject happens even when one doesn't really need or want it. It's also not great from a build hygiene perspective, as LLVM globally sets some flags