Draft: Bazel recursive stubgen example

[cemlyn007]

I made this branch mainly for another MR I am trying to merge with the help of @nicholasjng. If/when the nanobind-bazel MR can land, would you maintainers want this example merged as well?

It's meant to be a slight modification of the existing example to create an example sub-module and makes a small modification to the setup.py to copy files whilst preserving the module structure.

[nicholasjng]

Thanks for the addition! I think this is very valuable to have for nanobind-bazel.

I actually have write access to this repo, since I sometimes need to update the bazel branch when configurations change (or setuptools breaks again). If @wjakob agrees, I can take over all Bazel-related PRs on this repo.

[nicholasjng]

Hey @cemlyn007 , since rules_python just released v1.0.0 with a fix for the Windows library locations, I updated the setup.py (and some other files) accordingly to test if we can build nanobind on Windows with only a hermetic interpreter.

Could I ask you to rebase on current bazel? Then I'll merge this right after.

[wjakob]

If @wjakob agrees, I can take over all Bazel-related PRs on this repo.

I agree.

A tangent : would it make sense to advertise more broadly that there is a bazel branch on the master branch? This may not be obvious to visitors.

[nicholasjng]

Thanks! And sure, I can add a note to the readme or something similar.

[nicholasjng]

Note: I declared the dependency on nanobind_bazel to be against a stable release from BCR, since that is how most users will use the package. Instead of keeping the local_path_override in this repo, I will add it in nanobind-bazel CI.

Currently CI is all red, since we're passing arguments to stubgen that have not been implemented yet (PR is open already). Once nanobind-bazel v2.4.0 is out on the BCR, this will be fixed.