<div dir="ltr"><div class="gmail_extra">Hi Matthew,</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 17, 2014 at 10:30 PM, Matthew Gardiner <span dir="ltr"><<a href="mailto:mg11@csr.com" target="_blank">mg11@csr.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 class="">Todd Fiala 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">
Hey Matthew,<br>
<br>
I'm thrilled that you are trying to get a test Linux box up!<br>
<br>
The easiest way to run that depends on whether you're using cmake/ninja or configure/make. If you don't have a strong preference, going with cmake/ninja is definitely the faster way to go.<br>
<br>
In any event, you'll want to kick off the tests with either one of these, after you've done a full build (i.e. 'ninja' in the build dir or 'make' in the build dir):<br>
<br>
cmake/ninja:<br>
cd /your/build/dir<br>
ninja check-lldb<br>
<br>
</blockquote></div>
I think I'm going to stick with make for now, since I've never had any luck with cmake/ninja.<div class=""><br></div></blockquote><div><br></div><div>Ok. I'm eventually going to document our setup, at which point you can maybe try out cmake again. Using ninja as the builder is significantly faster (I think it was 20%+ faster for us over make).</div>
<div><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 class="">
<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">
configure/make:<br>
cd /your/llvm/dir<br>
cd tools/lldb/test<br>
make<br>
</blockquote>
<br></div>
Ok... From what you've just said. Does that mean I'll running the make in that tools/lldb/test runs the swig and python required to get lldb.py built?<div class=""><br></div></blockquote><div><br></div><div>Assuming I have the typical llvm, llvm/tools/clang and llvm/tools/lldb directory structure for the source, I make a sibling directory to llvm called build. I cd into that, type something like:</div>
<div>../llvm/configure --prefix=`pwd`/../install</div><div><br></div><div>Then I build with:</div><div>make -j32</div><div><br></div><div>(You'll want a j value that is something appropriate for your # cores - I typically use n, where n is the number of cores I have, 32 in this case).</div>
<div><br></div><div>That will build everything, including the lldb python module, liblldb.so (referenced by the lldb python module), and all the lldb exes.</div><div><br></div><div>Then I run make in the tools/lldb/test directory with this:</div>
<div>make -C tools/lldb/test</div><div><br></div><div>That should run all the tests for you.</div><div><br></div><div>If I got any of the details wrong, I think it is covered here under 'To build with autoconf' (including the autoconf-based testing):</div>
<div><br></div><div><a href="http://lldb.llvm.org/build.html">http://lldb.llvm.org/build.html</a><br></div><div><br></div><div>Hope that helps!</div><div><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 class="">
<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">
<br>
Both those incantations will get you a test run that does the tests without you needing to set up anything else (e.g. lldb/python paths, or architecture settings for the test run). They'll also run the tests faster if you have multiple cores on your dev box/VM.<br>
<br>
Let me know if you hit any trouble with that.<br>
</blockquote>
<br></div>
Yeah - will do. I'm going to try to focus this today.<div class=""><br></div></blockquote><div><br></div><div>Good luck!</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 class="">
<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">
Particularly the cmake configuration line - the basic cmake configuration line with minimal options has never worked well for me on Linux, so I call it with a bunch of flags to specify the llvm build type and a few other details.<br>
<br>
</blockquote></div>
No. I've never had much luck with cmake :-(<br>
<br></blockquote><div><br></div><div>Yeah, it took me several days to get my cmake setup working back on Ubuntu 12.04. It's a bit easier on Ubuntu 14.04.</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">
Anyway, I'm kicking off a fresh lldb build (i.e. configure in the out-of-tree build dir, then a make) now. And I'll postback later on today regarding my progress.<br>
<br>
Later<div class=""><div class="h5"><br>
Matt<br>
<br>
<br></div></div></blockquote><div>Let me know how it goes!</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 class=""><div class="h5">
<br>
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom<br>
More information can be found at <a href="http://www.csr.com" target="_blank">www.csr.com</a>. Keep up to date with CSR on our technical blog, <a href="http://www.csr.com/blog" target="_blank">www.csr.com/blog</a>, CSR people blog, <a href="http://www.csr.com/people" target="_blank">www.csr.com/people</a>, YouTube, <a href="http://www.youtube.com/user/CSRplc" target="_blank">www.youtube.com/user/CSRplc</a>, Facebook, <a href="http://www.facebook.com/pages/CSR/191038434253534" target="_blank">www.facebook.com/pages/CSR/<u></u>191038434253534</a>, or follow us on Twitter at <a href="http://www.twitter.com/CSR_plc" target="_blank">www.twitter.com/CSR_plc</a>.<br>
New for 2014, you can now access the wide range of products powered by aptX at <a href="http://www.aptx.com" target="_blank">www.aptx.com</a>.<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><table cellspacing="0" cellpadding="0" style="color:rgb(136,136,136);font-family:'Times New Roman'"><tbody><tr style="color:rgb(85,85,85);font-family:sans-serif;font-size:small">
<td nowrap style="border-top-style:solid;border-top-color:rgb(213,15,37);border-top-width:2px">Todd Fiala |</td><td nowrap style="border-top-style:solid;border-top-color:rgb(51,105,232);border-top-width:2px"> Software Engineer |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(0,153,57);border-top-width:2px"> <a href="mailto:tfiala@google.com" style="color:rgb(17,85,204)" target="_blank"><span style="color:rgb(34,34,34);background-color:rgb(255,255,204)">tfiala@google.com</span></a> |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(238,178,17);border-top-width:2px"><font color="#1155cc"> <a>650-943-3180</a></font></td></tr></tbody></table><br></div>
</div></div>