search for: llvmconfig

Hello. I am trying to install jllvm (http://code.google.com/p/jllvm/) on my gentoo linux system. I already have llvm-3.1 installed by the packager manager. The jllvm build mechanism uses the file LLVMConfig.cmake. There is no such file installed on my system. Therefore I cannot install jllvm. Checking the sources of llvm-3.1 and llvm-3.0 one find the files llvm-3.1.src/cmake/modules/LLVM-Config.cmake and llvm-3.1.src/cmake/modules/LLVMConfig.cmake.in. Why LLVMConfig.cmake is not installed? How can...

Hi all, CMake seems to have broken in the last few days - or is it just me? tcare:llvm-release tcare$ make -j4 -- Target triple: x86_64-apple-darwin10.5.0 -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Targeting X86 CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMARMAsmParser 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 (llvm_confi...

...in a pretty basic > chroot, should cmake be installed there? 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 LLVMExports.cmake Makefile ```` The ``LLVMConfig.cmake`` and ``LLVMConfigExports.cmake`` file are generated by the build in this directory and are later installed (along with a bunch of other files). When I do a build of LLVM on Arch Linux and install it in the inst...

Hi, Myself and a colleague of mine are trying to use LLVM's exported targets [1] on trunk and I've noticed that the generated CMake files (LLVMConfig.cmake and LLVMExport.cmake) are broken when trying to use Visual Studio 2015 (using CMake 3.2.1). ## Broken target properties in LLVMExports.cmake LLVM itself builds fine but when our project tries to do ``find_package(LLVM)`` we get the following error message (see [2] for context). ``` -- Loo...

--- autoconf/configure.ac | 4 +++- cmake/modules/LLVMConfig.cmake.in | 3 ++- configure | 4 +++- tools/llvm-config/Makefile | 6 ++++++ tools/llvm-config/llvm-config.in.in | 3 ++- 5 files changed, 16 insertions(+), 4 deletions(-) diff --git a/autoconf/configure.ac b/autoconf/configure.ac index f3e94e8..cd9...

Why? -eric On Sep 20, 2011, at 9:14 AM, Johannes Obermayr wrote: > --- > autoconf/configure.ac | 4 +++- > cmake/modules/LLVMConfig.cmake.in | 3 ++- > configure | 4 +++- > tools/llvm-config/Makefile | 6 ++++++ > tools/llvm-config/llvm-config.in.in | 3 ++- > 5 files changed, 16 insertions(+), 4 deletions(-) > > diff --git a/autoconf/configure.ac b/autoconf/confi...

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 (llvm_co...

*hi,Óscar:* * * *so following patch should address both the relocation problem and uninstall tree problem, not fully tested just for discussion.* * * Index: LLVMConfig.cmake.in =================================================================== --- LLVMConfig.cmake.in (revision 159425) +++ LLVMConfig.cmake.in (working copy) @@ -32,8 +32,11 @@ set(LLVM_ON_WIN32 @LLVM_ON_WIN32@) set(LLVM_INSTALL_PREFIX @LLVM_INSTALL_PREFIX@) -set(LLVM_INCLUDE_DIRS ${LLVM_INSTALL...

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/b...

> > *hi,Óscar:* > * * > >Why? Please describe a case. > > >I need to do some futher experiment and to see whether I have been > wrong. > Since I touch this problem several months ago, so I did some test using the 3.2svn, the reason why uninstalled build 'cmake not work lies in set(LLVM_INSTALL_PREFIX @LLVM_INSTALL_PREFIX@) set(LLVM_INCLUDE_DIRS

...folder. I don't know > how they do it but they don't use CMake so it won't really help to look it > up. And I want to only build those llvm libraries I will need for my > project. > > Am 10.10.2016 um 02:10 schrieb don hinton: > > 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...

...k 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 >> LLVMExports.cmake Makefile >> ```` > > > I have these for the test-release build, but only in the *.obj directory, > not the install directory. Okay. So that means the files are being generated during the build but not installed for some r...

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

...ng the DESTDIR makefile variable. I have sent a patch to llvm-commits to try to fix this [3]. The result of this mistake is that the CMake files end up containing absolute paths to the temporary tarball directory which means they cannot be imported by another project. Second, the LLVM CMake files (LLVMConfig.cmake and LLVMExports.cmake) are not relocatable (they contain absolute paths which are based on the install prefix). So even if the first issue is fixed we still have the problem that a user cannot simply extract the binary tarball to an arbitrary location their system and build the toy project ag...

The cmake files generated when building LLVM (including LLVMConfig.cmake) are to support cmake's find_package() [1] function. In the build dir the generated files are placed in <build-dir>/share/llvm/cmake. After install, in <prefix>/lib/llvm/share/llvm/cmake. CMake is not able to find them without a hint. CMake searches these paths on Unix: - &l...

On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner seeing

Hi, Is there a way to avoid linking with the dynamic LTO library. I’m using llvm 5.0.0 on various platforms (linux, windows, macOS), this library is not required by my application and I keep having trouble with it. My project is cmake based and makes use of LLVMConfig.cmake or llvm-config output (depending on the platform - there is no LLVMConfig.cmake with the windows package). On windows the LTO lib resolves to LTO-NOTFOUND, which obviously triggers an error at link time. On linux and MacOS, everything runs smoothly up to the install step: then I get an "...

...n) to generate one > Module and then use PassManager to add several passes. And my Makefile is > pretty simple, it looks like this: > > *********************************************************************************************** > all: parser > > OBJS = main.o \ > > LLVMCONFIG = llvm-config > CPPFLAGS = `$(LLVMCONFIG) --cxxflags` -std=c++11 > LDFLAGS = `$(LLVMCONFIG) --ldflags --system-libs` -lpthread -ldl -rdynamic > -ltinfo > LIBS = `$(LLVMCONFIG) --libs all` > > clean: > $(RM) -rf parser $(OBJS) > > %.o: %.cpp > g++ -g -c $(CPPFLAGS) -o $...

..."" CACHE PATH "Root of LLVM install.") IF (NOT EXISTS ${LLVM_ROOT}/include/llvm) MESSAGE (FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") ENDIF () SET (CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${LLVM_ROOT}/share/llvm/cmake") INCLUDE (LLVMConfig) LLVM_MAP_COMPONENTS_TO_LIBRARIES (REQ_LLVM_LIBRARIES jit native) ########################### Then, I try to cmake my project: % cmake .. -DLLVM_ROOT=/Applications/Development/llvm/ CMake Error at CMakeLists.txt:25 (INCLUDE): include could not find load file: LLVMConfig CMake Error at...

...utside build and then launch the build. IIUC there is a desire for Clang to be able to be built externally to LLVM rather than subsumed into its build process. The top-level CMakeLists.txt file of Clang already has code to do that, though it can be much cleaner after my patches to LLVM to provide LLVMConfig.cmake are integrated. Then it will even be possible to build Clang using CMake against a LLVM that was built and installed using configure+make. If one would like to drive compiler-rt as part of testing a Clang built outside of LLVM then the appropriate place for the ExternalProject_Add call woul...