llvm-project/mlir/cmake/modules
Stella Stamenova 438f805145 [mlir] Configure mlir so that it can be directly included in a parent cmakelists.txt
The goal is to allow a project to directly include the `CMakeLists.txt` of mlir via something such as `add_directory`. This currently doesn't work because the exported targets then end up being imported in the same top-level project and `cmake` is not happy. LLVM works around this by guarding the exports based on the existence of the `LLVMSupport` library. This change does the same using `MLIRSupport`. In our experience, no targets need to be added to the export in the case.

If there's a preferred way of doing this or a better lib to use as the main target to check for, please let me know.

Reviewed By: stellaraccident

Differential Revision: https://reviews.llvm.org/D117599
2022-01-19 12:02:22 -08:00
..
AddMLIR.cmake [mlir][cmake] Use `GNUInstallDirs` to support custom installation dirs 2022-01-19 17:11:04 +00:00
AddMLIRPython.cmake Re-apply "[mlir] Allow out-of-tree python building from installed MLIR." 2021-11-14 20:31:34 -08:00
CMakeLists.txt [mlir][cmake] Use `GNUInstallDirs` to support custom installation dirs 2022-01-19 17:11:04 +00:00
MLIRConfig.cmake.in [mlir] Configure mlir so that it can be directly included in a parent cmakelists.txt 2022-01-19 12:02:22 -08:00
MLIRDetectPythonEnv.cmake [mlir] Rework subclass construction in PybindAdaptors.h 2022-01-19 18:09:05 +01:00