similar to: [LLVMdev] Minor correction to the Visual Studio documentation/Windows support in general

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

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit

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

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

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 have several times over the past three months tried to retrieve the trunk version of LLVM/Clang/Compiler-RT from Subversion and then tried to build it on Windows: Without success. Also, I occasionally get emails from people who ask me why LLVM/Windows does not build (they find my name in the mailing list archive). This has made me ponder the issue and I came up with the following scheme

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

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!

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

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

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

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

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

Hi there, Sorry, I don't have the thread history to reply to since I normally read llvmdev through the archives, but wanted to give my .02 of feedback anyway. As far as I understand, this change is wanted because the LLVM infrastructure derives no value from knowing the types, and there's a cost in terms of code spent to support all of it. I've been creating a frontend that mostly

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

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

const uint64_t UnknownAddressOrSize <http://llvm.org/doxygen/namespacellvm_1_1object.html#abcfa9b6f24c69c52d2489a102ba3583c> = ~0ULL This found at line 260 in ObjectFile.h. Notice the 0ULL thingy. Cheers, Mikael -- Love Thy Frog! -------------- next part -------------- An HTML attachment was scrubbed... URL: