similar to: [LLVMdev] liblibclang.dll?

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

On 06/22/2012 07:42 AM, David Röthlisberger wrote: > On 22 Jun 2012, at 00:08, Óscar Fuentes wrote: >> > Albert Graef <Dr.Graef at t-online.de> writes: >> > - libclang ends up as liblibclang.so (building clang along with LLVM). >>> >> Surely that's not intended? >> > >> > There was some discussion about this on the past, but I

> > the problem is that very few LLVM developers use or know anything about > Windows. > The only way for this to change is for people who do know and care about > Windows > to step forward, work on improving Windows support, and contribute their > Windows > viewpoint to design discussions etc. > As it is now, Windows users will quite likely drop LLVM because of the

Hi, I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 1.6 GHz), but it seems rather odd that the system has been linking clang.exe for the past two hours. It appears that a couple of gigabytes of virtual memory are being used (causing constant swapping) - the system has only 2 GB of physical memory. Is this a bug in MINGW64 (binutils 2.22) or is it just too little RAM in

On Thu, May 24, 2012 at 12:53 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > One project I'd like to complete pretty soon is to go through the build > instructions, for mingw32, and see if I can't somehow create a mingw64 > build.  I believe the 32-bit platform is dying by the hour so I'm rather > eager to have a mingw64 version of LLVM/Clang.  Also, I'd love

Hi, I just did a "make install" on Win7x64 using Mingw64 and it dropped off the files in "C:\Program Files (x86)\LLVM". That's almost right, but nicer would be if the 64-bit build was dropped off in "C:\Program Files\LLVM". I am fairly confident that it is me who is doing something wrong because I simply do this: (retrieve trunk version of LLVM, Clang,

于 2012/5/27 11:04, Mikael Lyngvig 写道: > Hi, > > I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 > 1.6 GHz), but it seems rather odd that the system has been linking > clang.exe for the past two hours. It appears that a couple of > gigabytes of virtual memory are being used (causing constant swapping) > - the system has only 2 GB of physical memory.

Hi, I was wondering if you guys are using a tool of some sort for generating the HTML for LLVM or if you are writing it by hand? I am thinking of submitting some Windows-specific documentation because I honestly find it quite difficult to get things up and running with MINGW64. I may be daft, but so may others :-) As a former build master, I have a strong preference for documentation that

On Mon, Jun 18, 2012 at 12:25 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi all, > >     3. The document now covers 32-bit and 64-bit builds with MinGW tools (if > anybody know of an alternate BINARY distribution of MinGW64 than Drangon's > release, please let me know so I can include it in the document). As was once explained to me by Ruben Van Boxem, what you

Hi, [Synopsis: Mikael thinks Windows support is overlooked and that this is a strategic error. You can skip to the next mail now, if you'd like :-) Long, long, long mail follows.] Before I go on, I'd like to informally apologize for my many postings to this mailing list. I have no intentions of spamming it, but I still feel a need to grasp certain things that seem to be implied by the

Hi all, Here's an updated version of my proposed "Building with MinGW on Windows" document. In summary, the document gives a step-by-step description of how to build LLVM + Clang on Windows WITHOUT having Microsoft Visual Studio installed. The high-level goal of the document is to make life pleasant for those wonderful Windows users who desire to try out LLVM and/or Clang. I

Hi, I tried to do a build with CMake, Ninja, and MinGW32 and MinG64 respectively: MinGW32 failed on an missing sys/mman.h (POSIX-specific header): D:/test/llvm-trunk/projects/compiler-rt/lib/enable_execute_stack.c:13:22: fatal error: sys/mman.h: No such file or directory #include <sys/mman.h> ^ MinGW64 failed on an #error directive:

Thank you so much for your hard work! LLVM/Clang is in need of motivated Windows developers willing to put in the time to make the LLVM/Clang experience better on Windows :) Quick note on the reST: instead of using a construct like: **Notice:** If you only want to build 32-bit programs, you do **not** need to install MinGW64. Prefer to use the reStructuredText "admonitions" <

Hi, My Windows build slave is now up and running. The only thing that isn't set up correctly yet is the test phase. Given this: 1. "make check" works fine on Mingw64/Windows x64. 2. "make clang-test" reports a 29 unexpected failures: Expected Passes : 4617 Expected Failures : 30 Unsupported Tests : 10 Unexpected Failures: 29 And make then fails with

Yes, sorry, the LLVM CMake documentation :-) I don't think I am duplicating a large chunk; I am continuously trying to shave off extraneous and redundant stuff off my Windows-specific document. I just managed to shave off about six lines or so because I don't like the huge introduction and explanation of what MinGW is. Now that the document covers Ninja, there's even more reason for

A tiny question (I hardly know what Ninja is, but am looking forward to trying it out): Does the changes also work with MinGW builds? I've got a Windows buildbot slave that does nothing but building LLVM+Clang using MinGW64 all day, every day. Or, is it only for Visual Studio? 2012/6/13 Justin Holewinski <justin.holewinski at gmail.com> > Wow, this is seriously fast on Windows!

On Mon, Jun 18, 2012 at 6:25 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi all, > > Here's an updated version of my proposed "Building with MinGW on Windows" > document. In summary, the document gives a step-by-step description of how > to build LLVM + Clang on Windows WITHOUT having Microsoft Visual Studio > installed. The high-level goal of the

On Sat, Jun 9, 2012 at 12:40 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > Here's the final, confirmed working version of my Windows guide for how to > set up a MinGW buildbot slave. Please consider to include it in the > documentation on the LLVM website. > > Basically, it saves the newcoming Windows user about two or three days of >

Mikael Lyngvig <mikael at lyngvig.org> writes: > Hi, > > I was wondering if you guys are using a tool of some sort for generating > the HTML for LLVM or if you are writing it by hand? It is written by hand. > I am thinking of > submitting some Windows-specific documentation because I honestly find it > quite difficult to get things up and running with MINGW64. I may

Albert Graef <Dr.Graef at t-online.de> writes: > On 06/21/2012 04:22 PM, Óscar Fuentes wrote: >> About the "many features" that cmake lacks, can you provide a list, >> please? > > Generally it works fairly well, but here are some differences to the > autoconf-based build I noticed: > > - No 'make uninstall'. That is a real deal breaker if you