[LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
blunted2night at gmail.com
Fri Apr 13 12:27:28 CDT 2012
I wasn't say that deploying LLVM within a shared library didn't make sense,
just that the interface to that shared library should be targeted at the
application domain that it is being used within.
On Fri, Apr 13, 2012 at 10:24 AM, Paul Robinson <pogo.work at gmail.com> wrote:
> There are a variety of "real world situations," some of them would benefit
> shared-library packaging and some would not. Say you're building a set of
> tools for internal deployment in your large-ish organization.
> Factoring out the
> Clang/LLVM bits into a shared library can reduce memory footprint when
> multiple tools, reduce disk footprint which therefore reduces
> antivirus overhead,
> and so forth. The constant-flux aspect of the interface mostly means you
> deploy the libraries separately from the tools that use them, but so what?
> Logistically that's no different than how you would deliver static-linked
> On Fri, Apr 13, 2012 at 9:59 AM, Nathan Jeffords
> <blunted2night at gmail.com> wrote:
> > It seems to be that LLVM doesn't make sense as a shared library. The
> > surface area of the interface is massive, and in constant flux. I would
> > think in real world situations, a domain specific interface with a more
> > focused public interface would the right solution.
> > On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote:
> >> Hi,
> >> From what I have seen on this mailing list and elsewhere, it would seem
> >> that it isn’t possible to build LLVM as a shared library using Visual
> >> Still, I would imagine that quite a few people are or would be
> interested in
> >> it, so… is there any plan to support this any time soon? This, unless
> >> already supported in some way or another which I am not aware of…? I
> >> been able to build LLVM as a shared library using Autotools and GCC
> >> MinGW) on Windows (as well as on Linux and Mac OS X), so it would
> really be
> >> a shame if the same couldn’t be done using Visual C++…
> >> Cheers, Alan.
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LLVMdev