summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/commands/expression/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorPeter Collingbourne <peter@pcc.me.uk>2019-12-06 15:54:47 -0800
committerPeter Collingbourne <peter@pcc.me.uk>2019-12-06 18:24:23 -0800
commit198fbcb817492ff45946e3f7517de15e8cdf0607 (patch)
treef514b38c1e89980057a7e1b12816685862d2cecc /lldb/packages/Python/lldbsuite/test/commands/expression/call-function/TestCallUserDefinedFunction.py
parent7ac966240184e604c03a7caf62f070ebb2977498 (diff)
downloadbcm5719-llvm-198fbcb817492ff45946e3f7517de15e8cdf0607.tar.gz
bcm5719-llvm-198fbcb817492ff45946e3f7517de15e8cdf0607.zip
Driver: Don't look for libc++ headers in the install directory on Android.
The NDK uses a separate set of libc++ headers in the sysroot. Any headers in the installation directory are not going to work on Android, not least because they use a different name for the inline namespace (std::__1 instead of std::__ndk1). This effectively makes it impossible to produce a single toolchain that is capable of targeting both Android and another platform that expects libc++ headers to be installed in the installation directory, such as Mac. In order to allow this scenario to work, stop looking for headers in the install directory on Android. Differential Revision: https://reviews.llvm.org/D71154
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/expression/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud