search for: llvm_native_build

...ON_DEPENDS} ${target} PARENT_SCOPE) > endfunction() > > +if(LLVM_USE_HOST_TOOLS) > + add_custom_command(OUTPUT LIB_LLVMSUPPORT > + COMMAND ${CMAKE_COMMAND} --build . --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) > +endif(LLVM_USE_HOST_TOOLS) > + > macro(add_tablegen target project) > set(${target}_OLD_LLVM_LINK_COMPONENTS ${LLVM_LINK_COMPON...

...set(LLVM_COMMON_DEPENDS ${LLVM_COMMON_DEPENDS} ${target} PARENT_SCOPE) > endfunction() > > +add_custom_command(OUTPUT LIB_LLVMSUPPORT > + COMMAND ${CMAKE_COMMAND} --build . --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_COMPONENT...

...tion() >>> >>> +if(LLVM_USE_HOST_TOOLS) >>> + add_custom_command(OUTPUT LIB_LLVMSUPPORT >>> + COMMAND ${CMAKE_COMMAND} --build . --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) >>> +endif(LLVM_USE_HOST_TOOLS) >>> + >>> macro(add_tablegen target project) >>> set(${targe...

...ed when the file is included which should only be once. >> + add_custom_command(OUTPUT LIB_LLVMSUPPORT >> + COMMAND ${CMAKE_COMMAND} --build . --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) >> + endif(NOT TARGET NATIVE_LIB_LLVMSUPPORT) >> + >> add_custom_command(OUTPUT ${${project}_TABLE...

..._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 + 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(NOT TARGET NATIVE_LIB_LLVMSUPPORT) + add_custom_command(OUTPUT ${${project}_TABLEGEN_EXE} COMMAND ${CMAKE_COMMAND}...

...the tablegen makefile commands (I think) (cmake/modules/TableGen.cmake:113-117): add_custom_command(OUTPUT ${${project}_TABLEGEN_EXE} COMMAND ${CMAKE_COMMAND} --build ../.. --target ${target} --config Release DEPENDS CONFIGURE_LLVM_NATIVE ${target} WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} COMMENT "Building native TableGen...") My guess is that the clang and llvm tablegen builds are trying to place their output into the same folder, so depending on when the resulting library gets linked/moved one of the threads could be left dangling with a partially-completed lib...

...g ExternalProject would be a lot of work, and it would be a huge maintenance burden to the community. As a data point, the one place in LLVM where we don't use ExternalProject (and we should be) is the cross-compiling goop, and it is a gigantic mess (see: CrossCompile.cmake and every mention of LLVM_NATIVE_BUILD in TableGen.cmake). It is filled with bugs and in desperate need of disentangling. This is another one of my sins that I need to repent. I feel I should also point out that ExternalProject isn't a silver bullet. It isn't going to solve all our problems, and since it is one of the more acti...

The CrossCompile module is in a perpetual state of "when I get a chance...", and desperately needs some cleanup. The problem you are hitting is caused by setting CMAKE_SYSTEM_NAME. When you set that CMake sets a variable CMAKE_CROSS_COMPILING. That variable should only be set when your host OS doesn't match your target OS. Since LLVM needs to build host-capable tools there is some

...ctually designed for this use, and it has loads of functionality we don’t need. > > >> As a data point, the one place in LLVM where we don't use ExternalProject (and we should be) is the cross-compiling goop, and it is a gigantic mess (see: CrossCompile.cmake and every mention of LLVM_NATIVE_BUILD in TableGen.cmake). It is filled with bugs and in desperate need of disentangling. This is another one of my sins that I need to repent. > > Oh, so ExternalProject would also fix cross compilation!? I'm sold! :) And hopefully we can use it to make the optimized tablegen option more robu...

On Wed, Apr 27, 2016 at 10:54 AM Renato Golin via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On 27 April 2016 at 15:39, Rafael Espíndola <rafael.espindola at gmail.com> > wrote: > > Yes. It is a move to put linux developers in the same position as > > windows and OS X ones, which is a *very* reasonable thing to do. > > Apart from the fact that neither