aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp
diff options
context:
space:
mode:
authorJustin Lebar <jlebar@google.com>2016-09-09 21:01:02 +0000
committerJustin Lebar <jlebar@google.com>2016-09-09 21:01:02 +0000
commitb9e51397bfe1fdbf0f1ae444744a8958b985bcb4 (patch)
tree39cee36e526289648a8ecbac7a4fa413daa648a3 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp
parent4aff9e6d716172b800903c913b0917bec55fb4c5 (diff)
downloadllvm-b9e51397bfe1fdbf0f1ae444744a8958b985bcb4.zip
llvm-b9e51397bfe1fdbf0f1ae444744a8958b985bcb4.tar.gz
llvm-b9e51397bfe1fdbf0f1ae444744a8958b985bcb4.tar.bz2
[StreamExecutor] Make SE work with an in-tree LLVM build.
Summary: With these changes, we can put parallel-libs within llvm/projects and build as normal. This is kind of the minimal change I could figure out how to make while still making us compatible with llvm's build system. Some things I'm not thrilled about include: * The creation of a CoreTests directory (the macros really seemed to want this) * Pulling SimpleHostPlatformDevice.h into CoreTests. It seems to me this should live inside unittests/include, or maybe tests/include, but I didn't want to make that change in this patch. One important piece of work that remains to be done is to make $ ninja check-streamexecutor run all the tests. Right now the only way I've figured out to run the tests is $ ninja projects/parallel-libs/streamexecutor/unittests/StreamExecutorUnitTests $ projects/parallel-libs/streamexecutor/unittests/CoreTests/CoreTests Reviewers: jhen Subscribers: beanz, parallel_libs-commits, jprice Differential Revision: https://reviews.llvm.org/D24368 llvm-svn: 281091
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp')
0 files changed, 0 insertions, 0 deletions