[Lldb-commits] [lldb] r213158 - Add kalimba as a platform.
tfiala at google.com
Thu Jul 17 23:10:52 PDT 2014
On Thu, Jul 17, 2014 at 10:30 PM, Matthew Gardiner <mg11 at csr.com> wrote:
> Todd Fiala wrote:
>> Hey Matthew,
>> I'm thrilled that you are trying to get a test Linux box up!
>> 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.
>> 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):
>> cd /your/build/dir
>> ninja check-lldb
>> I think I'm going to stick with make for now, since I've never had any
> luck with cmake/ninja.
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).
>> cd /your/llvm/dir
>> cd tools/lldb/test
> 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?
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:
Then I build with:
(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).
That will build everything, including the lldb python module, liblldb.so
(referenced by the lldb python module), and all the lldb exes.
Then I run make in the tools/lldb/test directory with this:
make -C tools/lldb/test
That should run all the tests for you.
If I got any of the details wrong, I think it is covered here under 'To
build with autoconf' (including the autoconf-based testing):
Hope that helps!
>> 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.
>> Let me know if you hit any trouble with that.
> Yeah - will do. I'm going to try to focus this today.
> 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
>> No. I've never had much luck with cmake :-(
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.
> 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.
> Let me know how it goes!
> 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
> More information can be found at www.csr.com. Keep up to date with CSR on
> our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people,
> YouTube, www.youtube.com/user/CSRplc, Facebook,
> www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
> New for 2014, you can now access the wide range of products powered by
> aptX at www.aptx.com.
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-commits