summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py
diff options
context:
space:
mode:
authorBrian Gesiak <modocache@gmail.com>2017-09-27 21:37:33 +0000
committerBrian Gesiak <modocache@gmail.com>2017-09-27 21:37:33 +0000
commit88f2aa12d9c8677934329799026d866e2a1cfd1b (patch)
tree247ccd0cb6836822b7e008bfa55206b980c6b58e /lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py
parentcb15e22b3b4d39bd642bbaf3e3b5c4e2774259cc (diff)
downloadbcm5719-llvm-88f2aa12d9c8677934329799026d866e2a1cfd1b.tar.gz
bcm5719-llvm-88f2aa12d9c8677934329799026d866e2a1cfd1b.zip
[CMake] Fix typo: "in-tree" -> "in-source" (NFC)
Summary: *In-source builds* of LLVM, in which a user invokes `cmake` from within the LLVM source directory, or invokes `cmake -B/path/to/source/dir/of/llvm`, are explicitly checked for and disallowed by LLVM's `CMakeLists.txt`. *In-tree builds*, on the other hand, refer to when the source directories of projects such as Clang are nested within the `llvm/tools` source directory. These are not disallowed, and are in fact a common way of building LLVM and Clang. Revise the comment to match the logic underneath it: it checks for an "in-source build", not an "in-tree build". Reviewers: beanz Reviewed By: beanz Subscribers: mgorny Differential Revision: https://reviews.llvm.org/D38317 llvm-svn: 314348
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud