diff options
| author | Sam Clegg <sbc@chromium.org> | 2019-11-07 14:51:25 -0800 |
|---|---|---|
| committer | Sam Clegg <sbc@chromium.org> | 2019-11-12 10:08:40 -0800 |
| commit | 4230fa939021e7a85f3ec06a4b1d8c661dfe329b (patch) | |
| tree | 10799a22155c64ec24177237c59a63394b40af9a /lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py | |
| parent | ef150e2ea51960e4a9689850d16b2dda355cdcd8 (diff) | |
| download | bcm5719-llvm-4230fa939021e7a85f3ec06a4b1d8c661dfe329b.tar.gz bcm5719-llvm-4230fa939021e7a85f3ec06a4b1d8c661dfe329b.zip | |
[libcxxabi] Prevent cmake from removing our explicit system C++ include paths
We build with `-nostdinc++` and add our own header path via
`LIBCXXABI_LIBCXX_INCLUDES`. However cmake tried to be clever and if
`LIBCXXABI_LIBCXX_INCLUDES` happens to match the compilers system path
it will remove the `-I` flag meaning we can't access any C++ headers.
Ideally cmake would be able see that we are using `-nostdinc++` and
disable this behaviour.
Differential Revision: https://reviews.llvm.org/D69973
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py')
0 files changed, 0 insertions, 0 deletions
