search for: cmake_source_dir

...lled, which is the first command in each of our CMakeLists.txt project files. In order to solve this problem, as well as improve maintainability, I'd like to propose the following: * For all projects except llvm, move `cmake_minimum_required()` inside the standalone build if-branch, i.e., `if(CMAKE_SOURCE_DIR STREQUAL CMAKE_CURRENT_SOURCE_DIR)`, at the top of the CMakeLists.txt project file. This will prevent unnecessary calls `cmake_minimum_required()` for in-tree builds, and allow all sub-projects to use the same policies set by llvm. * Move all `cmake_policy()` commands out of llvm/CMakeLists.txt an...

...r, and until now I have used my own CMake build system for LLVM. But now LLVM has a CMake build system of its own, so when upgrading my LLVM version I decided to move to the 'official' one. It's not an easy transition, the build fails. I already found one bug: in some files the variable CMAKE_SOURCE_DIR is used for the LLVM top-level source directory, while LLVM_MAIN_SRC_DIR should be used instead. A small patch is attached for this. Now I get a failure for llvm-config: Scanning dependencies of target llvm-config.target [ 93%] Regenerating /home/kevin/Documents/ProgProj/hyper-llvm-new/build/com...

...SM}) + 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 the start of the configure (before any project command is run) and restore those values before starting the native configure, of course. This still feels pretty ugly though, a...

[I'm cc-ing the mailing list because there are some topics here of general interest] HyperQuantum <hyperquantum at gmail.com> writes: >> CMAKE_SOURCE_DIR should be the same as LLVM_MAIN_SRC_DIR. If you know an >> scenario where this is not true, please describe it. > > In my case it's not true. I have put LLVM in a subdirectory of my > project (./compiler/llvm-2.4/), so the top-level CMakeLists.txt of > LLVM isn't the actua...

On Fri, Jul 21, 2017 at 1:16 AM Reid Kleckner <rnk at google.com> wrote: > This is great news! Do we know who contributed the changes to cut the > extra library dependencies? > > Do you think we should remove ENABLE_OBJLIB to simplify our CMake files in > the near future? It seems to me that anyone who cares about highly parallel > build throughput can upgrade CMake to get

...ulator-0.7.4-orig/CMakeLists.txt tpm_emulator-0.7.4/CMakeLists.txt +--- tpm_emulator-0.7.4-orig/CMakeLists.txt 2012-09-17 13:16:27.832582475 -0400 ++++ tpm_emulator-0.7.4/CMakeLists.txt 2012-09-17 13:16:41.621654594 -0400 +@@ -63,6 +63,7 @@ + # include root directories + include_directories(${CMAKE_SOURCE_DIR}) + include_directories(${CMAKE_BINARY_DIR}) ++include_directories(../../vtpm_manager/manager) + + # add internal libraries + add_subdirectory(tpm) +diff -Naur tpm_emulator-0.7.4-orig/CMakeLists.txt.orig tpm_emulator-0.7.4/CMakeLists.txt.orig +--- tpm_emulator-0.7.4-orig/CMakeLists.txt.orig 1969...