fd5af7efad
`nanobind_INCLUDE_DIR` is only populated when MLIR discovers nanobind through the Python package. When `nanobind_DIR` is supplied explicitly, the variable remains unset and the configuration output contains an empty path: ``` Found nanobind v2.13.0: ``` The nanobind CMake package location is already reported by both discovery paths. We can only print the detected nanobind version in the final status message. Or maybe if we want we can find the include dir for the explicit path too and merge them to `nanobind_INCLUDE_DIR` but I think this is better. |
||
|---|---|---|
| .. | ||
| AddMLIR.cmake | ||
| AddMLIRPython.cmake | ||
| CMakeLists.txt | ||
| FindLevelZeroRuntime.cmake | ||
| Findocloc.cmake | ||
| FindSyclRuntime.cmake | ||
| IRDLToCpp.cmake | ||
| MLIRCheckHardwareFeatures.cmake | ||
| MLIRConfig.cmake.in | ||
| MLIRConfigVersion.cmake.in | ||
| MLIRDetectPythonEnv.cmake | ||