summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Fuzzer/FuzzerLoop.cpp
diff options
context:
space:
mode:
authorBruce Mitchener <bruce.mitchener@gmail.com>2015-10-09 03:40:55 +0000
committerBruce Mitchener <bruce.mitchener@gmail.com>2015-10-09 03:40:55 +0000
commit6ec5d61bdae112ef079f1c101bd50a26ffaeb0d3 (patch)
tree0ac8d8a66b618060a7ad47307872eb189acbb4f8 /llvm/lib/Fuzzer/FuzzerLoop.cpp
parent1825fac3c914ad555f87e8995cdb7d92c33fb55e (diff)
downloadbcm5719-llvm-6ec5d61bdae112ef079f1c101bd50a26ffaeb0d3.tar.gz
bcm5719-llvm-6ec5d61bdae112ef079f1c101bd50a26ffaeb0d3.zip
Fix handling of LLDB_VERS_GENERATED_FILE.
Summary: This is Darwin only. The symbol defined by ${LLDB_VERS_GENERATED_FILE} is used by source/lldb.cpp, so anything that uses lldb.cpp (which is in lldbBase) should also have the generated symbol. This means that the entire process can be centralized within source/CMakeLists.txt where lldbBase is constructed. Additionally, the custom command should have dependencies on the project file as well as the generation script so that if either changes, the version file is correctly re-generated and everything is re-linked appropriately. * cmake/LLDBDependencies.cmake: Remove everything related to the generated version file from here. * source/CMakeLists.txt: On Darwin, add the generated version file to the sources that make up lldbBase. Also, create a custom target and make lldbBase depend on it to re-generate the generated file as needed. * source/API/CMakeLists.txt: Don't need to build the generated version file here or use it to control linking against swig_wrapper. * tools/lldb-server/CMakeLists.txt: Likewise. Reviewers: dawn, sas, clayborg, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D13552 llvm-svn: 249806
Diffstat (limited to 'llvm/lib/Fuzzer/FuzzerLoop.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud