Hi Nikola,<div><br></div><div>Thank you very much for your feedback!</div><div><br></div><div>I am beginning to feel slightly dizzy from all the suggestions that go against each other :-)</div><div><br></div><div>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.</div>
<div><br></div><div>I'll use your link, thank you for that.</div><div><br></div><div>It is intended to be a brief, conscise, and precise tutorial on how to build LLVM and Clang using the MinGW tools. I believe that those who know more can easily skip parts whereas those who know less cannot easily figure out the missing parts. So I try to spell it out from A to Z. That way, anybody can read and use the document: The newbie as a safe guide and the expert as a checklist. </div>
<div><br></div><div>As for VS, well, I feel that it is of URGENT importance to inform the newbie that he or she cannot expect to get usable results with Microsoft Visual Studio (i.e. using Clang as the frontend and attempt to link a somewhat advanced C++ program). </div>
<div><br></div><div>Well, people are different. I do suffer from a very poor memory, which is what makes me so reluctant to actually code on LLVM or Clang, but I felt very confused and overwhelmed by the whole ordeal when I first entered the world of LLVM - even though I've used computers for three decades, Unix for 5+ years full-time, worked on other compiler projects, and so on, and so on. So just because you felt it was straightforward does not mean everybody will do so (emotional makeups are as different as people are). And I am trying to be gentle towards ever imaginable newbie. I know that it took me days to set up the first build slave because there were so many loose ends all over the place. And this document actually started out as a document on how to set up a Windows buildbot slave. Then it got chopped into two, now three documents. </div>
<div><br></div><div>I have to teach you a small verse here: ASS-U-ME is to make an ASS of U and ME. In other words: Every assumption in every document, line of code, space shuttle, whatever is going to cost dearly at some point later on. I am intentionally NOT assuming anything about the level of the user (actually, I am: I assume they know how to open up a console window on Windows, this assumption was introduced to shorten the document).</div>
<div><br></div><div>Well, the initial version WAS too long and covered lots of ground that ultimately only served to confuse the newbie. Thanks to the readers of these lists, those issues got sorted.</div><div><br></div>
<div>I hope I don't sound obtuse, hostile, or unfriendly. I think your points are generally very good and useful (and I will incorate most of them into the document), but I strongly disagree on the tutorial thingy :-)</div>
<div><br></div><div>-- Disclaimer: I am <b>not</b> arrogant in real life, so if you perceive me as being arrogant, you are to blame ;-)
</div><div><br><div class="gmail_quote">2012/6/18 Nikola Smiljanic <span dir="ltr"><<a href="mailto:popizdeh@gmail.com" target="_blank">popizdeh@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Jun 18, 2012 at 12:25 PM, Mikael Lyngvig <<a href="mailto:mikael@lyngvig.org">mikael@lyngvig.org</a>> wrote:<br>
> Hi all,<br>
><br>
</div><div class="im">> 3. The document now covers 32-bit and 64-bit builds with MinGW tools (if<br>
> anybody know of an alternate BINARY distribution of MinGW64 than Drangon's<br>
> release, please let me know so I can include it in the document).<br>
<br>
</div>As was once explained to me by Ruben Van Boxem, what you call mingw32<br>
should probably be called <a href="http://mingw.org" target="_blank">mingw.org</a> (or maybe only mingw). The other<br>
one should be called MinGW-w64. Also note that MinGW-w64 can target<br>
both 32-bit and 64-bit windows!<br>
<br>
I was also informed that nightly builds of mingw-w64 are rock solid,<br>
so here's a link to toolchain targeting Win64<br>
<a href="http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/release/" target="_blank">http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/release/</a><br>
<br>
As for the rest of the document I have only one complaint that's more<br>
a matter of style and taste. The document sounds like tutorial and is<br>
very different from say "getting started" which is more to the point.<br>
I'll try to be more concrete:<br>
<br>
"Building LLVM on Windows using the MinGW32 or MinGW64 toolchains can seem<br>
daunting at first."<br>
<br>
I never had this impression, you just checkout clang, unpack mingw,<br>
run cmake, run ming32-make. Also note that I knew next to nothing<br>
about mingw when I first did this.<br>
<br>
Mingw vs VS issues<br>
<br>
I think it would be fair to say that mingw is better supported without<br>
having to list every feature that doesn't work with VS (who will<br>
remember to change this page when the features get implemented?). I'm<br>
also assuming the person already knows why he wants to use mingw.<br>
<br>
Reference to "Getting Started"<br>
I think that Getting Started page should have a link to your document<br>
as the official Clang+Mingw information. You don't really need to<br>
refer back to Getting started, infinite loop anyone :)<br>
<br>
As Justin said, I would concentrate more on the official tools like ming32-make.<br>
<br>
The way I imagine this is:<br>
- explain how to choose mingw flavor<br>
- checkout llvm/clang<br>
- how to use cmake to generate makefiles<br>
- how to build using ming32-make<br>
- how to debug<br>
- how to run tests (python, gnuwin32, subversion)<br>
- mention alternative tools like ninja build<br>
<br>
As I said, this is just my personal preference, I just had the<br>
impression that your document was too long and covered a lot of ground<br>
that it didn't really have to.<br>
</blockquote></div><br><br>
</div>