search for: explicit_map_components_to_librari

....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_config) cmake/modules/AddLLVM.cmake:78 (add_llvm_executable) tools/llvm-mc/CMakeLists.txt:3 (add_llvm_tool) Tom

...gt; 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 documented): --- a/cmake/modules/LLVM-Config.cmake +++ b/cmake/modules/LLVM-Config.cmake @@ -160,7 +160,7 @@ function(explicit_map_components_to_libraries out_libs) list(REVERSE expanded_components) list(APPEND processed ${lib}) # Find the maximum index that doesn't have to be re-processed: - while(NOT "${expanded_components}" MATCHES "^${processed}.*" ) + while(NOT "${expanded_components}" MAT...

...set ( LLVM_LIB_DEPS * <lib-name> <dependency 1> ... <dependency n> ... ) Here '*' is used as a delimiter to specify where each library dependency list starts This allows to get both the list of libraries and dependency information from one source. It is done in the explicit_map_components_to_libraries function which uses LLVM_LIB_DEPS to populate llvm_libs and MSVC_LIB_DEPS_* if they are not defined thus allowing external use. Best regards, Victor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100314/6...

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_config) cmake/modules/AddLLVM.cmake:78 (add_llvm_executable) tools/llvm-mc/CMakeLists.txt:3 (add_llvm_tool) On Aug 2, 2010, at 11:12 AM, Tom Care wrote: > Hi all, > > CMake seems to...

...info/llvmdev>> writes: > > >/ This patch *seems* to fix the problem (cmake regexps are not thoroughly > />/ documented): > />/ > />/ --- a/cmake/modules/LLVM-Config.cmake > />/ +++ b/cmake/modules/LLVM-Config.cmake > />/ @@ -160,7 +160,7 @@ function(explicit_map_components_to_libraries out_libs) > />/ list(REVERSE expanded_components) > />/ list(APPEND processed ${lib}) > />/ # Find the maximum index that doesn't have to be re-processed: > />/ - while(NOT "${expanded_components}" MATCHES "^${processed}.*" ) &...

...gt; <dependency 1> ... <dependency n> > ... > ) > > Here '*' is used as a delimiter to specify where each library dependency > list starts > > This allows to get both the list of libraries and dependency information > from one source. It is done in the explicit_map_components_to_libraries > function which uses LLVM_LIB_DEPS to populate llvm_libs and MSVC_LIB_DEPS_* > if they are not defined thus allowing external use. Interesting idea. But this method does not take into account the case where the user does not build all libraries (i.e. ignores some LLVM targets). On this sc...

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.

...ackend 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 call first): cmake/modules/LLVMConfig.cmake:47 (explicit_map_components_to_libraries) cmake/modules/LLVMConfig.cmake:40 (explicit_llvm_config) cmake/modules/AddLLVM.cmake:82 (llvm_config) cmake/modules/AddLLVM.cmake:114 (add_llvm_executable) examples/Kaleidoscope/Chapter4/CMakeLists.txt:3 (add_llvm_example) -- Configuring incomplete, errors occurred! When I try the auto...

...re: http://clasg.llvm.org/get_started.html and, while running cmake, I get: > CMake Error at cmake/modules/LLVM-Config.cmake:141 (message): > Library `vectorize' not found in list of llvm libraries. > Call Stack (most recent call first): > cmake/modules/LLVM-Config.cmake:54 (explicit_map_components_to_libraries) > cmake/modules/LLVM-Config.cmake:47 (explicit_llvm_config) > tools/clang/CMakeLists.txt:192 (llvm_config) > tools/clang/lib/CodeGen/CMakeLists.txt:13 (add_clang_library) I tried Googl'ing for the error, but nothing. A little help? Note that I did successfully build LLVM wi...

Eli Gottlieb <eligottlieb at gmail.com> writes: > I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To > do so, I regenerated the JNI 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

Hi again, I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To do so, I regenerated the JNI 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): > eli at

...ncy n> > > ... > > ) > > > > Here '*' is used as a delimiter to specify where each library dependency > > list starts > > > > This allows to get both the list of libraries and dependency information > > from one source. It is done in the explicit_map_components_to_libraries > > function which uses LLVM_LIB_DEPS to populate llvm_libs and > MSVC_LIB_DEPS_* > > if they are not defined thus allowing external use. > > Interesting idea. But this method does not take into account the case > where the user does not build all libraries (i.e. ignores s...