v2.1.0

This release adds the nanobind_shared_library and nanobind_stubgen rules/macros, to allow C++ shared libraries containing a statically linked nanobind and automatic stub generation at build time, respectively.

From now on, users can bazel run //:mypkg/stubgen/target to build an extension and generate stubs for it at the same time. An example of this is given in the nanobind example.

Note: The nanobind_stubgen() rule can be considered experimental at this point. In particular, pattern files and non-standard output paths have not yet been exhaustively tested. Please raise an issue to report any bugs you experience with it!

What's Changed

• Propagate visibilities to created nanobind extension libs by @nicholasjng in #30
• Clarify usage instructions, Bazel version restrictions by @nicholasjng in #32
• Add nanobind_shared_library rule by @nicholasjng in #31
• Expose nanobind's stubgen as a py_binary by @nicholasjng in #35
• Add nanobind_stubgen to the project README by @nicholasjng in #36

Full Changelog: v2.0.0...v2.1.0

v2.0.0

This release enables building nanobind extensions in Bazel for nanobind v2.0.0, which was released recently.

Right now, stubgen is not yet implemented, since some questions around how to incorporate it into the build defs still linger.

v1.0.0

The first stable release of nanobind-bazel. Mirrors nanobind@v1 builds.