similar to: [LLVMdev] Windows strategy?

On Mon, Jun 11, 2012 at 10:52 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > [Synopsis: Mikael thinks Windows support is overlooked and that this is a > strategic error. ...] > Synopsis of my response: It is not overlooked, it has some technical, non-technical, and manpower limitations. Allow me to briefly summarize these issues: Technical: Currently, we have

Thanks for your extensive answer! I now better understand the processes involving LLVM and Clang. I figured you were like most FOSS projects: A group of dudes working more or less together towards a common objective and therefore wanted to try to tune that objective. I have contributed a Mingw64 Windows buildbot slave that fails predictably in 29 tests on each build, and I will happily offer

On Mon, Jun 11, 2012 at 1:52 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, Again, this is more of a topic for cfe-dev (copied). LLVM itself works very well on Windows; it's Clang that has issues. > > [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,

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, 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 experimentation to get it all working. I think those days are important as many people balk at spending days on figuring out how to get

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

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 >

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

Mikael Lyngvig <mikael at lyngvig.org> writes: [snip] > Yes, I am quite familiar with the CMake documentation, but why are you > asking? That's not the cmake documentation, that's the LLVM cmake documentation: a short document that tries to explain everything you need to know about cmake to build LLVM. I had the impression that you were duplicating a large chunk of the info

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" <

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

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,

> > 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

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

Does Clang/Clang++ not have its own set of standard headers? Isn't this a serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work in progress on this? Ideally, Clang would ship as a ready-to-use installation image that included everything needed to use it as the possibly best C and C++ compiler on the market. Or, am I ahead of myself again? Cheers, Mikael -- Love Thy

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:

On Mon, May 28, 2012 at 07:42:12PM +0200, Mikael Lyngvig wrote: > Does Clang/Clang++ not have its own set of standard headers? Isn't this a > serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work > in progress on this? It provides the compiler-centric headers. It doesn't replace the rest of the C runtime library. That wouldn't make much sense. Joerg

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

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

Mikael, Thanks for working on. My gross comments... - Canonical URL of LLVM project is; http://llvm.org/ , not www.llvm.org. - "test-suite and cygwin" could be split out. It would be special thing. - Memory/storage requirements would be moved to "A.B Debugging". Less memory would be enough without debug build. - Python (x64 binary) is available, too. I am using. Python