search for: llvm_map_components_to_librari

...--debug-output yields no additional information, and running cmake with gdb attached just gives me a backtrace with no signs of abnormal operation. I've tried the old "comment stuff out and see what causes the symptom to reappear" method of debugging, and it's definitely the llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES all) line in my CMakeLists.txt. I've attached CMakeLists.txt for reference. Could anyone perhaps tell me why CMake can't finish? Cheers, --Eli Gottlieb -------------- next part -------------- cmake_minimum_required (VERSION 2.6) project (jllvm) add_library(jllvm SHA...

...bindings from fresh LLVM 3.1 headers, and > did a slight rewrite of my CMakeLists.txt file for building the C > code. > > Problem is, cmake no longer finishes at all. I receive the > following output, and then it just runs forever (while still > responding to a CTRL-C): Yep, llvm_map_components_to_libraries gets confused by the existence of both gtest and gtest_main and enters an infinite loop. A workaround is to not pass "all" to llvm_map_components_to_libraries but a list of required components.

...M 3.2 (effortless upgrade, awesome stuff!) I thought I would try taking the MCJIT for a spin after having read that the JIT is considered to be "legacy". So the changes I made to my code were: + #include <llvm/ExecutionEngine/MCJIT.h> - #include <llvm/ExecutionEngine/JIT.h> + llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES mcjit native) - llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) However the following call now returns NULL: EngineBuilder(TheModule).setEngineKind(EngineKind::JIT).setErrorStr(&error).create(); There doesn't appear to be an EngineKind::MCJIT option. A...

On 1/21/2013 2:01 AM, Óscar Fuentes wrote: > Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > >> I was using the find_package(LLVM llvm/share/llvm/cmake) and >> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >> the libraries to link against. This works well for the libLLVM* >> libraries, but how do I implement similar find stuff for clang >> libraries? > > AFAIK, there is no such feature for Clang. > Thanks Oscar. ashok

...e ${LLVM_SOURCE_DIR}/include ) > > Replace LLVM_SOURCE_DIR/LLVM_BUILD_DIR with the respective directories. > Same for Clang Thanks for the response, it worked. I can now compile my code by adding the additional include paths. I was using the find_package(LLVM llvm/share/llvm/cmake) and llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get the libraries to link against. This works well for the libLLVM* libraries, but how do I implement similar find stuff for clang libraries? TIA, ashok

...works there are a few things I think we should fix before the LLVM 3.5 release. Here are the current issues I see that I'd like to discuss. Just to clarify by "Targets" I mean targets in the CMake sense (e.g.. an executable or a library) 1 - We currently have both the old way (i.e. llvm_map_components_to_libraries() as in [2] ) and the new way of using built LLVM targets in CMake projects in trunk. I think we should at some point remove the llvm_map_components_to_libraries() stuff because it's messy. I'm not convinced it should be done in the LLVM 3.5 release because it would probably be nicer to a...

...; 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 CMakeLists.txt:26 (LLVM_MAP_COM...

Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > I was using the find_package(LLVM llvm/share/llvm/cmake) and > llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get > the libraries to link against. This works well for the libLLVM* > libraries, but how do I implement similar find stuff for clang > libraries? AFAIK, there is no such feature for Clang.

On 1/21/2013 10:25 AM, Ashok Nalkund wrote: > On 1/21/2013 2:01 AM, Óscar Fuentes wrote: >> Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: >> >>> I was using the find_package(LLVM llvm/share/llvm/cmake) and >>> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >>> the libraries to link against. This works well for the libLLVM* >>> libraries, but how do I implement similar find stuff for clang >>> libraries? >> >> AFAIK, there is no such feature for Clang. I noticed that the f...

Óscar Fuentes <ofv at wanadoo.es> writes: > Yep, llvm_map_components_to_libraries gets confused by the existence of > both gtest and gtest_main and enters an infinite loop. A workaround is > to not pass "all" to llvm_map_components_to_libraries but a list of > required components. This patch *seems* to fix the problem (cmake regexps are not thoroughly docum...

...> On 1/21/2013 10:25 AM, Ashok Nalkund wrote: >>> On 1/21/2013 2:01 AM, Óscar Fuentes wrote: >>>> Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: >>>> >>>>> I was using the find_package(LLVM llvm/share/llvm/cmake) and >>>>> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >>>>> the libraries to link against. This works well for the libLLVM* >>>>> libraries, but how do I implement similar find stuff for clang >>>>> libraries? >>>> >>>> AFAIK, there is no such...

...>> include(LLVM) >> # Now set the header and library paths: >> include_directories( ${LLVM_ROOT}/include ) >> link_directories( ${LLVM_ROOT}/lib ) >> # Let's suppose we want to build a JIT compiler with support for >> # binary code (no interpreter): >> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native core) >> # Finally, we link the LLVM libraries to our executable: >> target_link_libraries(jllvm ${REQ_LLVM_LIBRARIES}) Where is the failure? On the "if( NOT EXISTS ${LLVM_ROOT}/include/llvm )" ? If that's the problem, is LLVM installed on...

On 01/17/2016 02:53 PM, Dan Liew wrote: > @Brad: CC'ing you because I know you use > ``llvm_map_components_to_libnames()`` so you will likely have > something to say about it breaking. I'm using it in CastXML but that could easily be adapted to something different if needed. The larger concern is that that API is the documented way to use LLVM in an application with CMake so

Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > We want to compile LLVM/Clang and use the resulting > headers/libraries in our project. But we compile it during out build > process. I can build LLVM/Clang by adding it to our cmakelists.txt but > when our code tries to use one of the headers > (clang/CodeGen/ModuleBuilder.h), its not found as it doesnt exist. If > I

Hi All, We want to compile LLVM/Clang and use the resulting headers/libraries in our project. But we compile it during out build process. I can build LLVM/Clang by adding it to our cmakelists.txt but when our code tries to use one of the headers (clang/CodeGen/ModuleBuilder.h), its not found as it doesnt exist. If I do a 'make install' in the llvm directory, then the file is

On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall > <David.Chisnall at cl.cam.ac.uk> wrote: >> On 5 Oct 2012, at 08:34, Jun Koi wrote: >> >>> any idea on how to fix the problem? >> >> The correct solution is to fix the LLVM build to install the .cmake files in a location that

...uired for Java and JNI. > FIND_PACKAGE(Java REQUIRED) > FIND_PACKAGE(JNI REQUIRED) > INCLUDE_DIRECTORIES(${JAVA_INCLUDE_PATH}) > INCLUDE_DIRECTORIES(${JAVA_INCLUDE_PATH2}) > # Let's suppose we want to build a JIT compiler with support for > # binary code (no interpreter): > llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native core) > # Finally, we link the LLVM libraries to our executable: > target_link_libraries(jllvm ${REQ_LLVM_LIBRARIES}) I run "cmake ." where I've got my source and then make. This results in: > eli at eli-netbook:~/Programs/decac/src/jllvm/llv...

On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 Oct 2012, at 08:34, Jun Koi wrote: > >> any idea on how to fix the problem? > > The correct solution is to fix the LLVM build to install the .cmake files in a location that CMake knows about. could you please elaborate? > The hacky solution that I've used is just to copy

...ake") #include(LLVMConfig) # Now set the header and library paths: include_directories( ${LLVM_INCLUDE_DIRS} ) link_directories( ${LLVM_LIBRARY_DIRS} ) add_definitions( ${LLVM_DEFINITIONS} ) # Let's suppose we want to build a JIT compiler with support for # binary code (no interpreter): # llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) # Finally, we link the LLVM libraries to our executable: target_link_libraries(myHello ${REQ_LLVM_LIBRARIES}) add_subdirectory(Hello) ##### and the content of Hello/CMakeLists.txt is like below: $ cat Hello/CMakeLists.txt cmake_minimum_required(VERSION 2.8) add_...