<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 17, 2012, at 7:23 PM, Óscar Fuentes wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">OTOH it's my personal<br>opinion that you may be explaining too much: it is not necessary to<br>explain, nor even mention, the different available build tools on<br>Windows. As LLVM and Clang are developer tools, one can suppose that the<br>user knows how to run a build.</span></blockquote></div><br><div>IMO, Mikael's efforts are on-target and very useful, and the level of detail is close to "right". Windows builds for almost any tool are, despite many of our most fervent desires, still very much different from linux builds. There are umpteen different variants on exactly which shims to select to make them work in the windows universe, and guidance through that maze is quite useful even to people familiar with all the options. In particular, the "it currently doesn't work with such-and-such" potentially saves false starts down those paths. </div><div><br></div><div>(Thanks Mikael!)</div></body></html>