Hi, I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: Linking CXX shared library ..\..\..\..\bin\liblibclang.dll "Liblib" seems a bit overkill. FYI. BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64: The v3.1 release does NOT build with Mingw64. I believe this has been fixed in the Subversion sources as they build without problems. There's a thread about this here http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-February/019968.html, Cheers, Mikael -- Love Thy Frog! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120528/45c776b1/attachment.html>
Mikael Lyngvig <mikael at lyngvig.org> writes:> Hi, > > I accidentally noticed the following line when building LLVM and Clang on > Windows 7 x64 using Mingw64: > > Linking CXX shared library ..\..\..\..\bin\liblibclang.dll > > "Liblib" seems a bit overkill. FYI.Search the clang ml archives for discussions about this. [snip]
On 28 May 2012, at 16:46, Mikael Lyngvig wrote:> > Hi, > > I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: > > Linking CXX shared library ..\..\..\..\bin\liblibclang.dll > > "Liblib" seems a bit overkill. FYI.See http://llvm.org/bugs/show_bug.cgi?id=12620 for links to several threads on the clang mailing list over the last 2 years. The latest change was trunk at r156809 -- it attempted to fix the cmake build system such that it builds "libclang" (not liblib...) on both Unixes and Windows. Does your version of Clang include this revision? Cheers, --Dave.
Here's the "svn info" output: c:\bld\llvm-trunk>svn info Path: . Working Copy Root Path: C:\bld\llvm-trunk URL: http://llvm.org/svn/llvm-project/llvm/trunk Repository Root: http://llvm.org/svn/llvm-project Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 Revision: 157599 Node Kind: directory Schedule: normal Last Changed Author: pcc Last Changed Rev: 157594 Last Changed Date: 2012-05-28 23:48:37 +0200 (ma, 28 maj 2012) I pulled this earlier today and the problem still exists for Mingw64/Win64 - that is, I have a file named liblibclang.dll in llvm-build/bin and liblibclang.dll.a in llvm-build/lib. Cheers, Mikael -- Love Thy Frog! 2012/5/29 David Röthlisberger <david at rothlis.net>> On 28 May 2012, at 16:46, Mikael Lyngvig wrote: > > > > Hi, > > > > I accidentally noticed the following line when building LLVM and Clang > on Windows 7 x64 using Mingw64: > > > > Linking CXX shared library ..\..\..\..\bin\liblibclang.dll > > > > "Liblib" seems a bit overkill. FYI. > > See http://llvm.org/bugs/show_bug.cgi?id=12620 for links to several > threads on the clang mailing list over the last 2 years. > > The latest change was trunk at r156809 -- it attempted to fix the cmake > build system such that it builds "libclang" (not liblib...) on both Unixes > and Windows. Does your version of Clang include this revision? > > Cheers, > --Dave. > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120529/17e9c9f7/attachment.html>
Possibly Parallel Threads
- [LLVMdev] liblibclang.dll?
- [LLVMdev] is configure+make dead yet?
- [LLVMdev] Minor correction to the Visual Studio documentation/Windows support in general
- [LLVMdev] Linking clang.exe takes more than two hours?
- [LLVMdev] Minor correction to the Visual Studio documentation/Windows support in general