llvm dev - Aug 2014 - [LLVMdev] Building LLVM as a shared library on MinGw (Makefiles)

The sed invocation in tools/llvm-shlib is stripping leading
underscores from symbols. This was breaking the windows dll build on
MinGw for me but I figure since it was in there it must work for
somebody. I'd like to figure out which configurations need the
underscore stripped and which don't. Is there anybody else building
DLLs under MinGw?

Thanks,
Keno

I didn't think it was possible to build an LLVM DLL on Windows, but maybe
I'm wrong.


On Thu, Jul 31, 2014 at 11:31 PM, Keno Fischer <kfischer at
college.harvard.edu
> wrote:
> The sed invocation in tools/llvm-shlib is stripping leading
> underscores from symbols. This was breaking the windows dll build on
> MinGw for me but I figure since it was in there it must work for
> somebody. I'd like to figure out which configurations need the
> underscore stripped and which don't. Is there anybody else building
> DLLs under MinGw?
>
> Thanks,
> Keno
> _______________________________________________
> 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...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140801/438815e6/attachment.html>

The shared library works fine here. I only made one modification to the
'tools/llvm-shlib/Makefile', because otherwise, two shared libraries
would
be created.

I've commented out the line 'SHARED_ALIAS := 1' from the Makefile.

Here is the command line i used to build LLVM/Clang:
../../configure --build=i686-w64-mingw32 --disable-assertions
--enable-keep-symbols --enable-optimized --enable-shared
--enable-targets=x86,x86_64

I used Mingw-w64 4.9.1 i686 posix + Clang r213454.

Sorry for my English.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140801/7e0e1f74/attachment.html>

Reid Kleckner <rnk at google.com> writes:
> I didn't think it was possible to build an LLVM DLL on Windows, but
maybe
> I'm wrong.
It is fairly easy with MinGW because gcc/ld can auto-(export/import) the
symbols. It is not as robust as explicitly declaring the visible symbols
(as VS requires) but it used to work well enough for creating an usable
monolithic LLVM.dll.