<div dir="ltr">Awesome, thanks Zachary!<div><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Sep 7, 2015 at 1:02 PM, Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>+Stephane because he just went through the pain of getting a working build on Windows, so he might be able to point out some gotchas.<br></div><div><br></div><div><b>About VS 2015</b></div>VS 2015 does not work because of Python. Technically, it could theoretically work but you won't be able to run the test suite at all. I don't plan to put a significant amount of effort into addressing this. Instead, this will be solved automatically if / when we address <a href="http://llvm.org/pr24461" target="_blank">http://llvm.org/pr24461</a>. You can use VS 2013 community edition though. TL;DR of the reason VS 2015 doesn't work is because a) Python and the program embedding python must be compiled with the same compiler, and b) Python doesn't compile with VS 2015 because it relies on implementation details of the CRT, which changed in 2015.<div><br></div></div></blockquote><div><br></div><div>Whoops, glad I did a VM snapshot before installing VS 2015 :-)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div><b>About Windows 10</b></div><div>The build shoudl work fine on Windows 10 x64. That's what I use every day. But you should still build an x86 LLDB, not an x64 one. x64 should work in theory (insofar as the build should succeed), but the actual runtime support isn't there yet so many things will fail.</div><div><br></div></div></blockquote><div><br></div><div>Okay great.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>A couple of things you might run into:</div><div><br></div><div>1) Make sure PYTHONHOME and PYTHONPATH are <b>not</b> set, otherwise LLDB's python and system python can run into conflicts.</div><div><br></div><div>2) Make sure you check out and build LLD, test executables must be linked with LLD or they will not have debug info. Also, make sure you specify LLDB_TEST_COMPILER on the cmake command line to point to a clang.exe (If you use a release clang then ninja check-lldb will be faster by an order of magnitude)</div><div><br></div><div>3) Make sure you build Python from source, run the install-custom-python.py, and specify -DPYTHON_HOME on the CMake command line. </div><div><br></div></div></blockquote><div><br></div><div>Very helpful, thank you! Especially the bits about clang speed. Since I'll be running in a VM, I'll appreciate any speed improvements I can get.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>Most of this is covered on the website build instructions, but I admit it's a lot of steps, and it's easy to miss one. Solving pr24461 should greatly simplify everything about building on Windows when I finally get around to it, but it's a lot of work. Still follow the build instructions anyway because there's other things as well, but the above 3 are probably the most likely to trip you up. </div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_quote"><div dir="ltr">On Mon, Sep 7, 2015 at 10:33 AM Todd Fiala via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>I've read the Windows lldb build instructions. I have a few questions just to verify before I put too much time into that end:</div><div><br></div><div>* Has the build been vetted on Windows 10 64-bit yet?</div><div><br></div><div>* Can Visual Studio 2015 Community Edition work as the compiler toolchain? (VS 2012+ is listed as okay, so I'm hoping yes).</div><div><div><br></div><div>Thanks!</div><span class=""><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></div></div><span class=""><font color="#888888">
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
</font></span></blockquote></div></div>
</blockquote></div><br>Now that I have a change ready that should not change behavior on Windows lldb, I was hoping to check it in and view the windows buildbots here:</div><div class="gmail_extra"><a href="http://lab.llvm.org:8011/builders">http://lab.llvm.org:8011/builders</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">But the two I found don't seem to run the test phase? They say they're skipping the test part if I read it right, and the compile ninja output doesn't look like it's snuck into that step. What's the right builder for me to look at for seeing Windows test results?</div><div class="gmail_extra">-- <br><div class="gmail_signature"><div dir="ltr">-Todd</div></div>
</div></div>