summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
diff options
context:
space:
mode:
authorMichal Gorny <mgorny@gentoo.org>2019-03-03 10:06:34 +0000
committerMichal Gorny <mgorny@gentoo.org>2019-03-03 10:06:34 +0000
commitd3516b51cae6f3ec38be2db718534f0446057b77 (patch)
tree886e4f75e391b4eecc4badce687d2098fafcaf3d /lldb/packages/Python/lldbsuite/test/functionalities
parentce686597722cecdecf9c33d0cfc3ba7909cd65b1 (diff)
downloadbcm5719-llvm-d3516b51cae6f3ec38be2db718534f0446057b77.tar.gz
bcm5719-llvm-d3516b51cae6f3ec38be2db718534f0446057b77.zip
[clang] [ToolChains/NetBSD] Support relative libc++ header path
Support locating the libc++ header files relatively to the clang executable, in addition to the default system path. This is meant to cover two use cases: running just-built clang from the install directory, and running installed clang from non-standard location (e.g. /usr/local). This is the first step towards ensuring that tests of more LLVM projects can work out-of-the-box within the build tree, and use the correct set of headers (rather than e.g. mixing just-built clang+libcxx with system install of libcxx). It avoids requiring the user to hack around missing include paths, or LLVM build system to replicate system-specific C++ library defaults in order to append appropriate paths implicitly. Differential Revision: https://reviews.llvm.org/D58592 llvm-svn: 355282
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud