similar to: [LLVMdev] LLVM Cmake module?

Eli Gottlieb <eligottlieb at gmail.com> writes: > So you're saying that the default CMake build of LLVM creates static > libraries that got linked into my shared-object and now require me to > link in everything they require myself? Shouldn't the linker be able > to track down C++ runtime for this? You told CMake to manage your shared library as if it were a pure C

After I actually get everything compiling, install the library, and load it from my Java program, I get the following: > Exception in thread "main" java.lang.UnsatisfiedLinkError: > /usr/lib/libjllvm.so: /usr/lib/libjllvm.so: undefined symbol: > _ZTVN10__cxxabiv120__si_class_type_infoE If I have to guess, this means that the CMake stuff given is linking to the C++ libraries

On Nov 4, 2010, at 11:48 AM, Óscar Fuentes wrote: > Eli Gottlieb <eligottlieb at gmail.com> writes: > >> So you're saying that the default CMake build of LLVM creates static >> libraries that got linked into my shared-object and now require me to >> link in everything they require myself? Shouldn't the linker be able >> to track down C++ runtime for

Eli Gottlieb <eligottlieb at gmail.com> writes: > I compiled and installed it to the prefix /usr, but that's not the > issue. Once I actually compile and install LLVM with CMake by hand, I > get the share/llvm/cmake stuff installed correctly (can those files be > included in "normal" builds, or will LLVM switch to CMake as its > primary build system?). Now

[Please CC the mailing list] Eli Gottlieb <eligottlieb at gmail.com> writes: > OK, I'm just going to paste in my CMakeLists.txt file. Like I said, > I'm building an LLVM install myself by untarring llvm, mkdir build in > the root dir of the source, cd build/, cmake .., make. > >> cmake_minimum_required (VERSION 2.6) >> project (libjllvm) >>

Well for one thing, it gives one example of a CMakeLists.txt file that correctly uses LLVM, and nothing else. It gives no information on how to find out what set of components I need to map for what APIs. Neither does llvm-config list out the names of the actual components. I can use either the CMake modules or llvm-config to find the library names once I've got the component names, but

I compiled and installed it to the prefix /usr, but that's not the issue. Once I actually compile and install LLVM with CMake by hand, I get the share/llvm/cmake stuff installed correctly (can those files be included in "normal" builds, or will LLVM switch to CMake as its primary build system?). Now I'm running into the problem of cflags or includes or something not being

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

So where could I find a list of LLVM libraries so I can figure out which ones I actually need to link into my program? Oscar Fuentes <ofv at wanadoo.es> writes: > Óscar Fuentes <ofv at wanadoo.es <http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>> writes: > > >/ This patch *seems* to fix the problem (cmake regexps are not thoroughly > />/ documented): >

Eli Gottlieb <eligottlieb at gmail.com> writes: > The two lines >> set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} >> "${LLVM_ROOT}/share/llvm/cmake") >> include(LLVM) > don't seem to work. I'm checking with installing LLVM from source to > see if that makes it work, but the LLVM install from the Ubuntu repos > doesn't seem to have a

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

sam lee <skynare at gmail.com> writes: > Hi, > > I built LLVM on Windows XP through cmake and MinGW make. That was a breeze! > Now, I wanted to start a project. > It seems like I need Makefile.rules and Makefile.config to start a new > project (from http://llvm.org/docs/Projects.html). Those files are unrelated to cmake. > And llvm/projects/sample uses autoconf (or

Ah, thank you so much. How did you get the list of target_link_libraries() ? Did you use llvm-config? If you did not have access to llvm-config, how would you get list of libraries to link to? Thanks. Sam On Sun, Jun 13, 2010 at 2:44 PM, Nathan Jeffords <blunted2night at gmail.com>wrote: > This isn't meant to be a sample, but I can share with you the cmake files I > use for my

Ó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 documented):

I built the list by hand though trial and error. I'm not sure if and how llvm-config works with cmake. Its seems now that I got the right dependencies in the right order, there have been no ongoing maintenance issues. On Sun, Jun 13, 2010 at 4:32 PM, sam lee <skynare at gmail.com> wrote: > Ah, thank you so much. > How did you get the list of target_link_libraries() ? > Did you

This isn't meant to be a sample, but I can share with you the cmake files I use for my compiler. It builds in both windows user MSVC, and linux using G++, but should work with MinGW. the structure is src/ CMakeLists.txt # root make file front/ CMakeLists.txt # library middle/ CMakeLists.txt # library back/ CMakeLists.txt # library npp/ CMakeLists.txt # executable

Hi All, I have a system running Linux x86_64. And I have the latest LLVM from the repo compiled and installed using CMake (2.8.10.2). In one of my projects, I need the LLVM libraries. So I use CMake to configure the compiler and linker flags ( Find_Package(LLVM Required) ). CMake is complaining about missing LLVM-Config when some users try to compile the project. I looked at the

On 09/09/2014 10:12 AM, Dan Liew wrote: > because my Linux distribution just upgraded to LLVM/Clang 3.5 and I > noticed that trying use find_package(LLVM ...) was broken :( AFAIK, that never worked in any version of LLVM not built by CMake before. That's why we taught cmake/modules/Makefile to generate LLVMConfig.cmake and LLVMExports.cmake. > What is happening is that none of the

On 17 March 2010 19:07, Óscar Fuentes <ofv at wanadoo.es> wrote: > Victor Zverovich <victor.zverovich at googlemail.com> writes: > > >> > Attached are two patches for the LLVM cmake build system. > >> > > >> > The first one adds static runtimes (MT and MTd) to the list of > >> > runtimes for the MSVC build. > >> >

Ubuntu 20.04 LTS will be released soon, and I believe it’ll have CMake 3.16.3, so that increases the LTS lower bound significantly. I strongly disagree with the sentiment that the build system already works so there’s no urgent need to improve it. I believe we should treat the build system like code, and the same ideas around refactoring apply. Our build system is a huge thorny mess; there’s tons