<div dir="ltr">This sounds awesome! It would be really great for developers that just want to use VS as well. No need to go and choose one of the various sets of Unix tools for Windows that are all slightly incompatible in different obscure ways.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 13, 2013 at 1:07 AM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
On 13/11/2013 01:06, Sean Silva wrote:<br>
<blockquote type="cite">
<div><br>
</div>
<div>
<div>+**Notice:** If you do not plan to run the test suite, or
sshd server, you don't</div>
<div>+need Cygwin. You can build LLVM + Clang with only
Subversion, MingwNN, and CMake.</div>
</div>
<div><br>
</div>
<div>I feel like the way you are handling these notices is
backwards. </div>
</blockquote>
<br>
This is all very complicated and difficult to document!<br>
<br>
I'd like to share an alternative..<br>
<br>
At Nuanti we have a setup that can run the full test suite natively
on Windows using only the native Microsoft toolchain and a special
BusyBox binary, so we don't even install MingW or Cygwin on Windows
development systems.<br>
<br>
This has a number of benefits:<br>
<ul>
<li>Full test coverage. Our BusyBox is patched to be compatible
with Unix so we get to run tests that would usually fail due to
REQURES/XFAIL mingw/shell/shell-preserves-root.</li>
<li>No need for Administrator access. There is nothing to install,
no GNU this or that, just a fresh SVN/git checkout from
<a href="http://llvm.org" target="_blank">llvm.org</a>.</li>
<li>Easy to set up. Just drop the single binary in your PATH or
lit folder.<br>
</li>
<li>Escaping and /dev/null hacks for Windows in lit are no longer
needed.</li>
<li>Full in-process execution. Forking is slow on Windows, but
with our approach a full test suite run is reduced close to
native timings comparable to other platforms.</li>
</ul>
I was planning to upstream this work later in the 3.5 cycle but
looking at how painful the process is at present, and more so the
effort to document it, I feel now like it might be worth pushing
ahead earlier.<br>
<br>
The patch to lit itself is very small / low-impact and most of the
work is in BusyBox itself.<br>
<br>
I can get this work Open Sourced along with a build of the drop-in
llvm-busybox.exe later today if it sounds desirable.<br>
<br>
Certainly it'd reduce much of this document to just "Copy
llvm-busybox.exe into your PATH"<br>
<br>
How does this sound?<br>
<br>
If you like the idea, let me know soon as today's the best time for
me to pull this all together and post the lit side of the work for
review.<br>
<br>
Regards,<br>
Alp.<span class="HOEnZb"><font color="#888888"><br>
<br>
<pre cols="72">--
<a href="http://www.nuanti.com" target="_blank">http://www.nuanti.com</a>
the browser experts
</pre>
</font></span></div>
<br>_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
<br></blockquote></div><br></div>