[LLVMdev] Shared library support of llvm
ripzonetriton at gmail.com
Wed May 8 15:04:49 PDT 2013
On Wed, May 8, 2013 at 8:55 PM, Morten Ofstad <morten at hue.no> wrote:
> Actually, adding a LLVM_EXPORT macro would be positive for other
> environments, because you can then build LLVM
> as a shared library with -fvisibility=hidden and use LLVM_EXPORT to only
> make public symbols visible. There are several
> advantages to this, as noted here:
I agree, this would be useful even for other environments to solve the
bloat that can happen by exporting all the symbols.
Adding targeted dllexport annotations won't work because non-Windows
developers (the majority) shouldn't be burdened with keeping them up
On Wed, May 8, 2013 at 5:21 PM, Reid Kleckner <rnk at google.com> wrote:
> Adding targeted dllexport annotations won't work because non-Windows
> developers (the majority) shouldn't be burdened with keeping them up
> to date.
IMHO it's not that big of a burden, we have build bots that can signal
whatever problems come up. And it would also be useful for other platforms.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev