aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/SymbolicFile.cpp
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2017-09-20 16:01:50 +0000
committerZachary Turner <zturner@google.com>2017-09-20 16:01:50 +0000
commit3dd2356b3aa227aa241ab4c7e4da11d5df1045f6 (patch)
tree691bfbe153e654337e1efe632bda07c802b329d6 /llvm/lib/Object/SymbolicFile.cpp
parent1d5d44ff05066739d95f48617ba0c12d827bc600 (diff)
downloadllvm-3dd2356b3aa227aa241ab4c7e4da11d5df1045f6.zip
llvm-3dd2356b3aa227aa241ab4c7e4da11d5df1045f6.tar.gz
llvm-3dd2356b3aa227aa241ab4c7e4da11d5df1045f6.tar.bz2
Make libcxx tests work when llvm sources are not present.
Despite a strong CMake warning that this is an unsupported libcxx build configuration, some bots still rely on being able to check out lit and libcxx independently with no LLVM sources, and then run lit against libcxx. A previous patch broke that workflow, so this is making it work again. Unfortunately, it breaks generation of the llvm-lit script for libcxx, but we will just have to live with that until a solution is found that allows libcxx to make more use of llvm build pieces. libcxx can still run tests by using the ninja check target, or by running lit.py directly against the build tree or source tree. Differential Revision: https://reviews.llvm.org/D38057 llvm-svn: 313763
Diffstat (limited to 'llvm/lib/Object/SymbolicFile.cpp')
0 files changed, 0 insertions, 0 deletions