I am excited about LLVM potentially using nanobind_bazel to build the MLIR library extensions for use in Python bindings applications, as shown the newest attempt to land a MODULE.bazel file (see PR llvm/llvm-project#164891).

But their current nanobind BUILD file is different from the one I have here, namely in the fact that they give both NB_SHARED and NB_BUILD for the libnanobind build. This issue is tracking support for these settings in nanobind_bazel, perhaps with the addition of a new feature flag. Admittedly, I have to find out what they exactly do first.

What I also need to investigate is whether setting these defines means we HAVE to produce a shared library artifact from the nanobind cc_library target.