[lldb-dev] ninja check-lldb failing due to lldb.py

David Blaikie dblaikie at gmail.com
Mon Mar 16 20:21:26 PDT 2015


I have a standard source layout:

llvm
 \- src
   \- tools
     \- clang
     \- lldb
 \- build
   \- ...


llvm/build$ ninja check-lldb
This script requires lldb.py to be in either
llvm/src/tools/lldb/build/Debug/LLDB.framework/Resources/Python,
llvm/src/tools/lldb/build/Release/LLDB.framework/Resources/Python, or
llvm/src/tools/lldb/build/BuildAndIntegration/LLDB.framework/Resources/Python.
Some tests might fail."

What do these 3 directories have to do with anything when my build
directory is llvm/build, not llvm/src/tools/lldb/build ? & is this a manual
step I'm meant to undertake? (could we automate it?)

(& the check-lldb target doesn't have dependencies on all the tools
required to run the tests either - which isn't quite right (compared to
check-llvm, check-clang, etc))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150316/41c6614d/attachment.html>


More information about the lldb-dev mailing list