similar to: [LLVMdev] CMake broken?

Tom Care <tcare at apple.com> writes: > This was after starting with an empty build directory. It seems to > work if I omit -DLLVM_TARGETS_TO_BUILD=X86, but a few days ago this > was working with just this target. Yep. I can replicate the problem on Linux with mkdir foo && cd foo cmake -DLLVM_TARGETS_TO_BUILD=X86 ../llvm I'll investigate a bit.

I'm seeing this as well, but for the LLVMAlphaAsmParser: CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMAlphaAsmPrinter not found in list of llvm libraries. Call Stack (most recent call first): cmake/modules/LLVMConfig.cmake:27 (explicit_map_components_to_libraries) cmake/modules/LLVMConfig.cmake:20 (explicit_llvm_config) cmake/modules/AddLLVM.cmake:61

I am using LLVM as back end for my compiler, 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

Hi all, I understand from the document that I should be able to configure llvm with only specific targets by passing -DLLVM_TARGETS_TO_BUILD=some-backend to cmake. However, I get the following errors whenever I don't include X86 in the target list: CMake Error at cmake/modules/LLVMConfig.cmake:127 (message): Library `X86' not found in list of llvm libraries. Call Stack (most recent

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm

On Mon, Feb 8, 2016 at 12:45 PM, Hans Wennborg <hans at chromium.org> wrote: > Chris Bieneman is probably your best bet, and maybe also Dan Liew. > Hans, My current, and hopefully final, revision of the proposed patch is simplified and reworked to solve the problem entirely from cmake without touching the the llvm-build python scripts. Basically, the new fix for avoiding the

I updated to the latest revision and now llvm does not build and quits cmake with CMake Error at cmake/modules/LLVMProcessSources.cmake:83 (message): Found unknown source file ../llvm-revec/lib/CodeGen/MachineFunctionAnalysis.cpp Please update ../llvm-revec/lib/CodeGen/CMakeLists.txt Thanks On Sat, Sep 3, 2016 at 2:09 AM, Craig Topper <craig.topper at gmail.com> wrote: >

On 6 July 2015 at 10:34, Ben Pope <benpope81 at gmail.com> wrote: > On 7 July 2015 at 01:12, Dan Liew <dan at su-root.co.uk> wrote: >> >> >> @Ben Pope: Your uploaded binary tarball is the odd one out. Any idea >> as to why the CMake files are missing and why the root directory name >> inside the tarball is not consistent with the uploaded tarballs for

Hi all. I want to use llvm in my project and I want to make llvm a git submodule in my project. http://llvm.org/docs/CMake.html#embedding-llvm-in-your-project At this in the documentation it claims to describe how to embed llvm into a project. I tried it that way but it doesn't work, because there isn't any findLLVM.cmake in the llvm/cmake/modules directory anymore (i don't

Sorry my example wasn't helpful. I did take a quick look at rust -- though I didn't download or try to build it -- and they seem to allow you to use an installed or prebuilt version in addition to building it in-tree. However, even when they build it in-tree, they build the whole thing -- see mk/llvm.mk. Good luck... On Mon, Oct 10, 2016 at 1:33 AM, Timo Janssen via llvm-dev <

hi, i am wondering if this link is still updated? http://www.llvm.org/docs/CMake.html#developing-llvm-pass-out-of-source i follow the instruction from the link, and create in my ~/test/ directory the CMakeLists.txt with following content: $cat test/CMakeLists.txt find_package(LLVM) # Define add_llvm_* macro's. include(AddLLVM) add_definitions(${LLVM_DEFINITIONS})

Hans, I have posted a complete patch for solving the linkage issues with LLVM_LINK_LLVM_DYLIB on Phabricator at http://reviews.llvm.org/D16945. The bulk of the fix the simple changes of... Index: cmake/modules/AddLLVM.cmake =================================================================== --- cmake/modules/AddLLVM.cmake (revision 259743) +++ cmake/modules/AddLLVM.cmake (working copy) @@

On Fri, 5 Oct 2012 13:04:46 +0530 Jun Koi <junkoi2004 at gmail.com> wrote: > i am wondering if this link is still updated? > > http://www.llvm.org/docs/CMake.html#developing-llvm-pass-out-of-source > > i follow the instruction from the link, and create in my ~/test/ > directory the CMakeLists.txt with following content: > <snip> > CMake Warning at

Hi, attached is a patch to improve including targets other than X86 in CMake MSVC builds. When adding libs to link, rather than always using LLVMX86CodeGen and LLVMX86AsmPrinter, it grabs the correct ones. It also adds "force-link-ints" to the various TargetMachine cpp files, as well as X86AsmPrinter and PPCAsmPrinter. These are needed to be able to encourage the Win32 linker to

Hi Ben, Thanks for taking the time to look at this. >> It's not necessary for CMake to be installed when building with the >> Autoconf/Makefile build system. If you look in the build directory >> after a build has been performed you should see in cmake/modules >> >> ``` >> LLVMBuildExports.cmake LLVMConfig.cmake LLVMConfigVersion.cmake >>

[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

Hi, I've taken a look at the binary tarballs for clang+llvm-3.6.2-rc1-* that have been uploaded and observed the following: * All uploaded tarballs include the generated CMake files apart from ``clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz``. These files (share/llvm/cmake/*.cmake) are missing in this tarball. * Inside the Ubuntu tarball the directory is not consistently named

Hello, I work on CMake upstream. I'd like to find out in what ways CMake upstream does not fit the needs of llvm/clang, and then fill those gaps. The recent update of the minimum version to CMake 2.8.8 is a good start. Before being able to assess what is missing, it should be ensured that the current codebase is as modern as the minimum version allows, and it needs to be cleaned up. 1)

On 11/14/2017, 01:26 AM, Chris Bieneman wrote: > Sorry for the delayed response. I've been out of town a lot lately. > > The documentation you referenced is unfortunately out of date (you might notice it still references autoconf). I'll see if I can find time to update it, but the guidance should be to use the `llvm_config` CMake function instead. The proper usage of that in the

On Thu, Oct 18, 2012 at 7:22 PM, Sameer Sahasrabuddhe <sameer.sahasrabuddhe at amd.com> wrote: > On Fri, 5 Oct 2012 13:04:46 +0530 > Jun Koi <junkoi2004 at gmail.com> wrote: > >> i am wondering if this link is still updated? >> >> http://www.llvm.org/docs/CMake.html#developing-llvm-pass-out-of-source >> >> i follow the instruction from the link,