similar to: [LLVMdev] "ninja update" not working.

On Mon, Jun 18, 2012 at 2:32 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > The docs state that you can do a "make update" to update all top-level and > embedded projects from Subversion. This is a feature of the configure+make build system, and not a feature of the CMake build system. I also don't have any real desire to support it as part of the

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 Christoph, It is a good question even though it is obvious :-) No, for the last few days, I have not been able to build Clang with make -j2 or -j4 - the build always fails on a ranlib operation. Also, on Windows, GNU Make seems to be somewhat broken with respect to parallel builds: It doesn't change a thing whether you specify -j2 or -j4 on a quad-core machine (with hyper-threading

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

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

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 Sun, Jun 17, 2012 at 7:30 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Christoph, > > It is a good question even though it is obvious :-)  No, for the last few > days, I have not been able to build Clang with make -j2 or -j4 - the build > always fails on a ranlib operation. > > Also, on Windows, GNU Make seems to be somewhat broken with respect to >

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

Christoph Erhardt <christoph at sicherha.de> writes: > Hi Mikael, > >> My Clang build used to take 59:29 minutes using MinGW Makefiles. With >> Ninja, it takes 18:43 minutes! That's a speed up of factor three. > sorry for asking the obvious question: Are you comparing against a > parallel "make -j<n>"? :-) I'm pretty sure he isn't.

I am building with MinGW and my experience is that "make -jN" either doesn't work (because of problems with different processes updating the same library using ranlib or something like that). And then there's the issue I mentioned in the previous doc. I think Ninja is a gift from some heavenly dimension. Others may disagree. But I think any Windows developer should take a

On Mon, Jun 18, 2012 at 11:46 AM, Chandler Carruth wrote: > On Mon, Jun 18, 2012 at 2:32 AM, Mikael Lyngvig wrote: >> >> Hi, >> >> The docs state that you can do a "make update" to update all top-level and >> embedded projects from Subversion. > > > This is a feature of the configure+make build system, and not a feature of > the CMake build

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, Nov 16, 2013 at 9:15 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM > Notice: You only need Ninja for the test build; none of the official LLVM builders use Ninja as far as I know. My buildbots use ninja. > Please notice that you must specify the absolute path to ninja, otherwise CMake

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 Nikola, Thank you very much for your feedback! I am beginning to feel slightly dizzy from all the suggestions that go against each other :-) I'll fix the documentation so that it uses MinGW and MinGW-W64. I'll ignore that the 64-bit version targets both 32-bit and 64-bit Windows, so as to keep things simple. I'll use your link, thank you for that. It is intended to be a brief,

It wouldn't take me more than an hour or two to do the format conversion. It is rather trivial, actually. Just say the word and I'm on to it like a starving bee. I guess I should get used to using the Sphinx layout; I'm simply more familiar with the format I use on my own websites. Have you guys ever considered making a less formal wiki for LLVM documentation - a place where tiny

Thanks for spotting those errors! Fixed. If you feel that this doc should be part of the LLVM documentation, perhaps in a revised form, just let me know. I am willing to convert it into reST and also to go through a peer review, but I simply cannot spend hundreds of hours munging about, rewriting, and retesting over and over as I am already busy on other documentation and other sub-projects.

On Sun, Nov 17, 2013 at 5:17 AM, Sean Silva <chisophugis at gmail.com> wrote: > > > > On Sun, Nov 17, 2013 at 3:50 AM, Mikael Lyngvig <mikael at lyngvig.org>wrote: > >> It wouldn't take me more than an hour or two to do the format conversion. >> It is rather trivial, actually. Just say the word and I'm on to it like a >> starving bee. I

On Sun, Nov 17, 2013 at 12:53 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Thanks for spotting those errors! Fixed. > > If you feel that this doc should be part of the LLVM documentation, > perhaps in a revised form, just let me know. I am willing to convert it > into reST and also to go through a peer review, but I simply cannot spend > hundreds of hours munging