diff options
| author | Markus Böck <markus.boeck02@gmail.com> | 2022-08-03 10:46:52 +0200 |
|---|---|---|
| committer | Markus Böck <markus.boeck02@gmail.com> | 2022-08-03 10:47:14 +0200 |
| commit | 34e814a00cb071059b9f7626c9456891409075ac (patch) | |
| tree | 828923351ac5330c8f287a87480f5173fb35d0a1 /llvm/lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp | |
| parent | 2fe3589acdbb87a6beb6173bb9b56d1bdab95d6a (diff) | |
| download | llvm-34e814a00cb071059b9f7626c9456891409075ac.zip llvm-34e814a00cb071059b9f7626c9456891409075ac.tar.gz llvm-34e814a00cb071059b9f7626c9456891409075ac.tar.bz2 | |
[CMake] Make split-file an utility instead of tool
`split-file` is essentially a development tool used for writing tests. Other related tooling for this purpose such as `FileCheck`, `count`, `not` and more are already created via `add_llvm_utility` instead of `add_llvm_tool`. The later is more meant as LLVM tools used as part of a toolchain (eg. `llvm-ar`), not for tools for the development of LLVM itself.
The main semantic difference this makes is that `split-file` is now built and installed via the `LLVM_INSTALL_UTILS` and `LLVM_BUILD_UTILS` instead of `LLVM_BUILD_TOOLS` and `LLVM_INSTALL_TOOLS` cmake flags. That way one can use `LLVM_BUILD_TOOLS=OFF LLVM_INSTALL_UTILS=ON` and have `split-file` installed along side the other testing tools.
Differential Revision: https://reviews.llvm.org/D130977
Diffstat (limited to 'llvm/lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp')
0 files changed, 0 insertions, 0 deletions