[Mlir-commits] [mlir] [MLIR][Python] Avoid printing an unset nanobind include directory (PR #211240)

[Anutosh Bhat]

https://github.com/anutosh491 created https://github.com/llvm/llvm-project/pull/211240

`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.

>From e7a5080584e736bfaae74b233b81ee913063d499 Mon Sep 17 00:00:00 2001
From: anutosh491 <andersonbhat491 at gmail.com>
Date: Wed, 22 Jul 2026 17:18:18 +0530
Subject: [PATCH] [MLIR][Python] Avoid printing an unset nanobind include
 directory

---
 mlir/cmake/modules/MLIRDetectPythonEnv.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mlir/cmake/modules/MLIRDetectPythonEnv.cmake b/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
index 068d6712393c2..4d99c8be0de7f 100644
--- a/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
+++ b/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
@@ -83,7 +83,7 @@ macro(mlir_configure_python_dev_packages)
       set(nanobind_INCLUDE_DIR "${PACKAGE_DIR}")
     endif()
     find_package(nanobind 2.9 CONFIG REQUIRED)
-    message(STATUS "Found nanobind v${nanobind_VERSION}: ${nanobind_INCLUDE_DIR}")
+    message(STATUS "Found nanobind v${nanobind_VERSION}")
     message(STATUS "Python prefix = '${PYTHON_MODULE_PREFIX}', "
             "suffix = '${PYTHON_MODULE_SUFFIX}', "
             "extension = '${PYTHON_MODULE_EXTENSION}")