similar to: [LLVMdev] Minor correction to the Visual Studio documentation

2012/5/24 Mikael Lyngvig <mikael at lyngvig.org>: > I know that the documentation says that I am to install GnuWin32 tools, but > I strongly oppose that idea.  We Windows people have our own tools and > practices and I think the LLVM developers should open up to a more > multi-platform approach than the current (Unix then, perhaps maybe, Windows) > approach.  CMake works

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

Oh, didn't realize that there already is a semi-official build of CMake with Ninja support. I am trying it out right now and it seems very promising. So I'll change the document to use Ninja instead of "MinGW Makefiles". No need to waste energy on MinGW and MSYS Makefiles when Ninja outdoes them both. I thought people would have to build CMake themselves, something I'd

On Sat, Jun 16, 2012 at 3:29 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Takumi, > > THANK YOU for your excellent review! It makes all the work worthwhile in > itself. > > It is getting "late" here (it is early morning) so I am about to call it a > day. But I will contemplate and incorporate your suggestions tomorrow, and > send you a full

Hi Takumi, THANK YOU for your excellent review! It makes all the work worthwhile in itself. It is getting "late" here (it is early morning) so I am about to call it a day. But I will contemplate and incorporate your suggestions tomorrow, and send you a full reply. I think I originally wrote a document where I addressed both Visual Studio and MinGW, but then decided that there were

As for Ninja, I'd like to wait until it is officially part of the released CMake. As I understand it, Windows support has been checked into the CMake repository but no offical release supporting Ninja has been made yet. I just retrieved Ninja from Github and this time it built without problems. 2012/6/16 NAKAMURA Takumi <geek4civic at gmail.com> > Mikael, > > Thanks for

Now I can't make CMake use "MSYS Makefiles". I get an error about GNU v4.7.0 being broken as it can't build a simple test program. Using "MinGW Makefiles", everything works out of the box. And I am trying to give the user the most Windowsy experience (to avoid Cygwin, GnuWin32, and MSYS, if I can). So I think I'll stick to my current angle - which is to let the

Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this

For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of

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

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

I checkout LLVM and clang from SVN, then use CMake to generate project files for Visual Studio 2010 (I started with 2008). The LLVM project compiles successfully and gives me all the tools including Clang. For a few tests, I compile C++ code with Clang which if I need to I link, I use MinGW's ld passing all the relevant object files and libraries including correctly ordering the start-up code

Now I recall what the problem was that I had: My code makes use of the Win32 API and that means pulling in Windows.h, which again pulls in some headers that make use of the force_inline thingy, which is not supported under Windows yet. I guess if I stuck with portable code, I could probably use Clang for Windows. Once again, I have to visit the thinking box and figure out what to do. But thanks

As for memory/storage, I think you want these presented as early as possible so people don't go setting up a box only to find out, half a week later, that they can never do what they intended to do (build Clang in debug mode). The reason I use 32-bit Python is that it is what you need, if you want to make a Windows buildbot slave because the Win32 bindings are needed and I don't think

Hi, I stumbled across three warnings in LLVM when building with MS Visual Studio 2010. It has been my experience that different compilers detect different things, so I thought I'd pass them on to you (in case your compiler does not warn about these things): warning C4805: '==' : unsafe mix of type 'bool' and type 'unsigned int' in operation

Hello Mikael, > Now I recall what the problem was that I had: My code makes use of the Win32 > API and that means pulling in Windows.h, which again pulls in some headers > that make use of the force_inline thingy, which is not supported under > Windows yet. Or you can use windows.h from mingw :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint

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

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

Wow, this is seriously fast on Windows! I've been using Ninja on Linux/Mac for awhile now, I'm glad to see it working on Windows now. On Wed, Jun 13, 2012 at 5:09 PM, =?utf-8?Q?=C3=93scar_Fuentes?= < ofv at wanadoo.es> wrote: > Nikola Smiljanic <popizdeh at gmail.com> writes: > > > Could somebody please provide more info. What exactly is ninja (I'm > >