diff options
author | Shoaib Meenai <smeenai@fb.com> | 2018-12-03 20:05:11 +0000 |
---|---|---|
committer | Shoaib Meenai <smeenai@fb.com> | 2018-12-03 20:05:11 +0000 |
commit | f75f88d090c46a7fd9da3c966678e19f2c301a55 (patch) | |
tree | eb5ea4f3458ca34b9e5cec16ac9eb902f2646f92 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp | |
parent | a79303d9a6a67ca2472471959ec2d636a56adb27 (diff) | |
download | bcm5719-llvm-f75f88d090c46a7fd9da3c966678e19f2c301a55.tar.gz bcm5719-llvm-f75f88d090c46a7fd9da3c966678e19f2c301a55.zip |
[cmake] Clean up add_llvm_subdirectory
I found the pattern of setting the project_BUILD variable to OFF after
processing the project to be pretty confusing. Using global properties
to explicitly keep track of whether a project has been processed or not
seems much more straightforward, and it also allows us to convert the
macro into a function (which is required for the early return).
Factor the project+type+name combination out into a variable while I'm
here, since it's used a whole bunch of times.
I don't believe this should result in any functional changes.
Differential Revision: https://reviews.llvm.org/D55104
llvm-svn: 348180
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp')
0 files changed, 0 insertions, 0 deletions