Greg Clayton wrote:
We should fix the detest.py to possibly look at the configure logs or do
something so it can figure out all the right stuff if that is possible by
looking at the lldb source directory. If this isn't possible, we should provide
a nice message on each platform with the common things we need to supply.
Matthew, feel free to add code to dotest.py that will make this clearer for
future test runners.
Ok.. I'll look into this, at some stage. Given the different build
systems and the different OSes, the "nice message" option. But I'll want
I can do.
Matt
Just recently I figured out how to successfully run dotest.py on a 64-bit
linux. I ran it from the command line as follows:
$ my-lldb-source-directory/test >
LD_LIBRARY_PATH=/my-build-directory/lib/
PYTHONPATH=/my-build-directory/lib/python2.7/site-packages/
python dotest.py --executable=/my-build-directorybin/lldb -v --compiler=gcc -q .
The above incarnation took some time to figure out!
<..snipped>
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
www.twitter.com/CSR_plc.
New for 2014, you can now access the wide range of products powered by aptX at
www.aptx.com.
_______________________________________________
lldb-dev mailing list
lldb-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
