search for: cmake_command

...ake/modules/TableGen.cmake > @@ -70,6 +70,15 @@ function(add_public_tablegen_target target) > set(LLVM_COMMON_DEPENDS ${LLVM_COMMON_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) &gt...

...dules/TableGen.cmake > +++ b/cmake/modules/TableGen.cmake > @@ -70,6 +70,13 @@ function(add_public_tablegen_target target) > 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) > + >...

...5 @@ function(add_public_tablegen_target target) >>> set(LLVM_COMMON_DEPENDS ${LLVM_COMMON_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_LLVMSUPP...

...;> >> + 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 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_LLVMSU...

...++ 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 + DEPENDS CONFIGURE_LLVM_NATIVE + WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} + COMMENT "Building libLLVMSupport for native TableGen...") + add_custom_target(NATIVE_LIB_LLVMSUPPORT DEPENDS LIB_LLVMSUPPORT) +...

...gen 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): 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 s...

...lding a native version of TableGen, but the way that's currently set up in cmake isn't working here. I'm looking at cmake/modules/CrossCompile.cmake (and I think "toochain" on the first line is a typo?) and trying to figure out how to make its call to execute_process(COMMAND ${CMAKE_COMMAND} ...) not inherit the top-level settings for CMAKE_C_COMPILER etc from the cross build. Any ideas? I've tried moving my mingw settings from the command line to a toolchain file but that hasn't done anything different so far. I've also tried specifically creating a native toolchain file...

...rnalProject.cmake;hb=v2.8.12.2#l846 > > so that flags like -j propagate automatically. You could do > that too: > > if(CMAKE_GENERATOR MATCHES "Make") > set(check_compiler_rt "$(MAKE)" "check-all") > else() > set(check_compiler_rt ${CMAKE_COMMAND} --build . > --target check-all --config $<CONFIGURATION>) > endif() > > ExternalProject_Get_Property(compiler-rt BINARY_DIR) > add_custom_target(check-compiler-rt > COMMAND ${check_compiler_rt} > DEPENDS compiler-rt > WORKING_DIRECTORY ${BINARY...

Hi Brad, Thanks for investigating this. Do you think it makes sense to land my ExternalProject_Add patch so that others can experiment with it? I can add quit with a fatal_error/warning if the build tree rules are generated with Ninja. However, there is a problem with Unix Makefiles as well: parallelism doesn't work when I run "make check-compiler-rt -j8" in the original build tree,

...ang-tblgen can be built set(external_clang_dir "-DLLVM_EXTERNAL_CLANG_SOURCE_DIR=${LLVM_EXTERNAL_CLANG_SOURCE_DIR}") endif() + unset(ENV{ASM}) + unset(ENV{CC}) + unset(ENV{CXX}) execute_process(COMMAND ${CMAKE_COMMAND} ${build_type_flags} -G "${CMAKE_GENERATOR}" -DLLVM_TARGETS_TO_BUILD=${LLVM_TARGETS_TO_BUILD} ${CROSS_TOOLCHAIN_FLAGS_${target_name}} ${CMAKE_SOURCE_DIR} It would be more proper to save the values of these environment variables at...

...flags like -j propagate automatically. You could do > >> that too: > >> > >> if(CMAKE_GENERATOR MATCHES "Make") > >> set(check_compiler_rt "$(MAKE)" "check-all") > >> else() > >> set(check_compiler_rt ${CMAKE_COMMAND} --build . > >> --target check-all --config $<CONFIGURATION>) > >> endif() > >> > >> ExternalProject_Get_Property(compiler-rt BINARY_DIR) > >> add_custom_target(check-compiler-rt > >> COMMAND ${check_compiler_rt} > >&...

...ableGen, but the way that's currently set up in cmake isn't working >> here. I'm looking at cmake/modules/CrossCompile.cmake (and I think >> "toochain" on the first line is a typo?) and trying to figure out how >> to make its call to execute_process(COMMAND ${CMAKE_COMMAND} ...) not >> inherit the top-level settings for CMAKE_C_COMPILER etc from the cross >> build. Any ideas? I've tried moving my mingw settings from the command >> line to a toolchain file but that hasn't done anything different so far. >> I've also tried specifical...

...gt; >> >> that too: > >> >> > >> >> if(CMAKE_GENERATOR MATCHES "Make") > >> >> set(check_compiler_rt "$(MAKE)" "check-all") > >> >> else() > >> >> set(check_compiler_rt ${CMAKE_COMMAND} --build . > >> >> --target check-all --config $<CONFIGURATION>) > >> >> endif() > >> >> > >> >> ExternalProject_Get_Property(compiler-rt BINARY_DIR) > >> >> add_custom_target(check-compiler-rt > >&gt...

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...reate the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=5 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=2 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/usr/local/google/home/blaikie/install/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/usr/local/google/home/blaikie/install/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/usr/local/google/home/blaikie/install/bin/ctest //ADVANCED pr...