similar to: [LLVMdev] cmake and custom pass

Hi, Is it possible to generate pass (shared object) from Cmake? I tried to use add_llvm_library() however it produces only static libs. Thanks, Mariusz.

mg <mariusz.grad at googlemail.com> writes: > Is it possible to generate pass (shared object) from Cmake? ? Please name the library or libraries you want to build as shared objects. > I tried to use add_llvm_library() however it produces only static > libs. As mentioned on http://www.llvm.org/docs/CMake.html : cmake -DBUILD_SHARED_LIBS=ON path/to/llvm/source This builds all

On Jul 24, 2013, at 14:18, Charles Davis <cdavis5x at gmail.com> wrote: > > On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote: > >> I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. >> >> There are a couple of issues that I still haven't been able to work out yet

arrowdodger <6yearold at gmail.com> writes: >> Or to say it with other words: patches welcome. > > So, how should i proceed? Make CMake-generated config to be identical to > autotools one? That would be a good thing. Please note that some checks are a bit tricky. A function that on platform A is on header foo.h on another platform may be on bar.h. Furthermore, cmake's

On 2009-05-24 20:38, Chuck Robey wrote: > Óscar Fuentes wrote: > >> Chuck Robey <chuckr at telenix.org> writes: >> >> >>>> Just checked that the makefiles generated by cmake work with `make' on >>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>>> missing. >>>>

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> Isn't is possible for cmake just to glob everything in the corresponding >>> directory? >>> >> >> Yes, but then the build would not notice a change on the file >> structure. You'll need to explicitly invoke cmake for being sure that >> whatever changes were made by the last svn

Török Edwin wrote: > On 2009-05-24 20:38, Chuck Robey wrote: >> Óscar Fuentes wrote: >> >>> Chuck Robey <chuckr at telenix.org> writes: >>> >>> >>>>> Just checked that the makefiles generated by cmake work with `make' on >>>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > >>>> Isn't is possible for cmake just to glob everything in the corresponding >>>> directory? >>>> >>>> >>> Yes, but then the build would not notice a change on the file >>> structure. You'll need to explicitly invoke

Hello, I currently write my own LLVM (function) pass and intend to use the following project to enable the use of range analysis information in my code: https://code.google.com/p/range-analysis/. Since I use Eclipse (with CMake) to build LLVM I did the following: 1. Provide each subfolder with a CMakeLists.txt (add_llvm_loadable_module). 2. Re-create the CMake config (cmake ../llvm -G

[ Please CC me I am not subscribed to this ML ] Original posting from [1]... <QUOTE> On Thu, Feb 25, 2016 at 05:13:05PM +0100, Sedat Dilek via llvm-dev wrote: > Build-time increased approx. 1h from 2 to 3 hours when using CMAKE > instead of CONFIGURE/MAKE (logs deleted for LLVM v3.8.0rc2). > Building always done with one single parallel-compile-jobs. > When using CMAKE

Paul Melis wrote: > Hi, > > Óscar Fuentes wrote: >> Chuck Robey <chuckr at telenix.org> writes: >> >> >>>> Just checked that the makefiles generated by cmake work with `make' on >>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>>> missing. >>>> >>> They

On Jan 5, 2011, at 6:34 AM, Óscar Fuentes wrote: > arrowdodger <6yearold at gmail.com> writes: > >>> Or to say it with other words: patches welcome. >> >> So, how should i proceed? Make CMake-generated config to be identical to >> autotools one? > > That would be a good thing. > > Please note that some checks are a bit tricky. A function that

Hi Tim, Thanks for your suggestion! I built LLVM with Debug and tried this with my custom pass. But it has the following error error: unable to load plugin '../../trace-extractor/build/TracePass.so': '../../trace-extractor/build/TracePass.so: undefined symbol: _ZTIN4llvm10ModulePassE’ Originally I used a builtin Clang in the system and it does not produce this issue. When I search

> I think it is a bit too soon to mark it as deprecated, but I hope to be in a position to mark > it as deprecated sometime this fall. So hopefully, yes it will be deprecated before the 3.8 > branch and hopefully we can remove it after the 3.8 release. That said, I think there is still > a healthy bit of work before we get to a point where I am comfortable marking it as deprecated.

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > [snip] > >> My internal priority for that CMake patch is low, as I need only minimal >> patching to use the autoconf-generated configure script to build LLVM. >> Right now it's just llvm.config.in.in that needs patching (the failsafed >> GenLibDeps.pl script went in

Dear all, I want to build an LLVM pass by using CMake. After reading the ralevant part of the documentation ( http://llvm.org/releases/3.1/docs/CMake.html#passdev), I copied the files in the llvm/lib/Transforms/Hello to another folder in order to give a try. Then I renamed the folder as Hello2. Then I have changed CMakeLists.txt as following: cmake_minimum_required(VERSION 2.8) # A

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

Kenneth Boyd <zaimoni at zaimoni.com> writes: [snip] >> That does not really surprise me about CMake, but then mingw is not a >> primary compiler on Windows, more so is VC++ or Intel, either way a >> bug should be submitted to the CMake devs. > I do not want to troll the CMake devteam, so I will not submit the bug > report without a full-blown patch. The CMake

On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote: > I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. > > There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at

Óscar Fuentes wrote: > "Anton Korobeynikov" <asl at math.spbu.ru> writes: > > >>> at all, it would be great if you reflect your changes on the file list >>> inside the corresponding CMakeLists.txt when you add, remove or rename >>> a .cpp file. >>> >> Isn't is possible for cmake just to glob everything in the