[llvm-dev] Building a program with LLVM on Unix

Russell Wallace via llvm-dev llvm-dev at lists.llvm.org
Wed Mar 23 11:01:50 PDT 2016


Thanks!

Bearing in mind that I don't know m4, looking at the code, it seems to work
by allowing an override to specify where to find llvm-config (which is the
right thing to do, of course) but by default looking in the current path.

Based on both my own limited experience in the matter and what David Jones
and David Chisnall are saying, one could argue that the path version
probably will _not_ be the correct one. That the correct default is
actually more likely to be e.g. ~/llvm-3.8. Does that make sense?

On Wed, Mar 23, 2016 at 4:51 PM, Diego Novillo <dnovillo at google.com> wrote:

> There are several m4 macros that let you write autoconf detection for
> llvm.  I recently needed to implement one.  Have a look here:
>
> https://github.com/google/autofdo/blob/master/m4/ax_llvm.m4
>
>
> Diego.
>
> On Wed, Mar 23, 2016 at 12:48 PM, Russell Wallace via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Building LLVM itself involves Cmake, but what's the best way to build a
> C++
> > program that needs to link with the LLVM libraries?
> >
> > If you're trying to optimise for making life as easy as possible for
> users
> > and people creating binary packages, in the normal course of events,
> > autotools is recommended. But the tutorial mentions running llvm-config
> to
> > get things like library paths - does autotools know how to do this?
> >
> > (I mostly use Windows, not as familiar with Unix, so please let me know
> if
> > the question I'm asking is not quite the same as the question I should be
> > asking.)
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160323/c6a69a1c/attachment-0001.html>


More information about the llvm-dev mailing list