aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne@apple.com>2020-06-26 12:08:59 -0400
committerPetr Hosek <phosek@google.com>2021-03-30 14:06:11 -0700
commitc06a8f9caa51c7ea71dac716e0a35f5e343e4546 (patch)
tree99c01001fe019bf7fe47750c5661f293d8da1bd4 /lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp
parent3a6365a439ede4b7c65076bb42b1b7dbf72216b5 (diff)
downloadllvm-c06a8f9caa51c7ea71dac716e0a35f5e343e4546.zip
llvm-c06a8f9caa51c7ea71dac716e0a35f5e343e4546.tar.gz
llvm-c06a8f9caa51c7ea71dac716e0a35f5e343e4546.tar.bz2
[libc++] Include <__config_site> from <__config>
Prior to this patch, we would generate a fancy <__config> header by concatenating <__config_site> and <__config>. This complexifies the build system and also increases the difference between what's tested and what's actually installed. This patch removes that complexity and instead simply installs <__config_site> alongside the libc++ headers. <__config_site> is then included by <__config>, which is much simpler. Doing this also opens the door to having different <__config_site> headers depending on the target, which was impossible before. It does change the workflow for testing header-only changes to libc++. Previously, we would run `lit` against the headers in libcxx/include. After this patch, we run it against a fake installation root of the headers (containing a proper <__config_site> header). This makes use closer to testing what we actually install, which is good, however it does mean that we have to update that root before testing header changes. Thus, we now need to run `ninja check-cxx-deps` before running `lit` by hand. Differential Revision: https://reviews.llvm.org/D97572
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions