jasonmolenda added a comment.
I've been meaning to look at this - for the command line style "cd test;
./dotest.py" approach, we could use similar logic to what
packages/Python/lldbsuite/test/dotest.py does in getOutputPaths() where it
finds an lldb binary in the "typical" location. for an Xcode style build, this
would be in a directory like ../llvm-build/Release+Asserts/x86_64/bin/FileCheck
where the build-style ("Release+Asserts") is going to vary but I'm guessing
that the build configuration of the FileCheck binary picked is not important.
https://reviews.llvm.org/D53175
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
