How do I make the bindings for one nanobind-binded library dependent on another?

[dograt]

For example, say I have the C++ library B that is dependent on library A.

I want library A to have its own standalone bindings for classes/functions, etc.

I also want library B to have its own bindings, via the b_bindings library, some of which will be dependent on types from library A (which has its own a_bindings library).

How do I go about accomplishing this without causing type conflicts, or being duplicative? I can't simply link library a_bindings into library b_bindings and call it a day like I would for the C++ libraries. I tried this just to see what would happen, and I get an unsurprising error message when attempting to link one nanobind module into another:

-- Target A linker options: $<$<CONFIG:Release>:>;$<$<CONFIG:Debug>:>;$<$<CONFIG:Release>:>;$<$<CONFIG:Debug>:>;$<$<CONFIG:Release>:>;$<$<CONFIG:Debug>:>
  -- Target A linker definitions: link_definitions-NOTFOUND
  -- Configuring A_bindings
  -- Adding A_bindings extension module a_ext
  -- Configuring B python bindings
  -- Adding B_bindings extension module b_ext
  CMake Error at projects/b/CMakeLists.txt:54 (target_link_libraries):
    Target "a_ext" of type MODULE_LIBRARY may not be linked into another
    target.  One may link only to INTERFACE, OBJECT, STATIC or SHARED
    libraries, or to executables with the ENABLE_EXPORTS property set.


  -- Configuring incomplete, errors occurred!

  *** CMake configuration failed
  error: subprocess-exited-with-error

This makes sense, but leaves me scratching my head. I want to distribute these sets of bindings separately, i.e., not as a single library, but I want them to be interoperable with the types defined in library A.

[dograt]

@wjakob This question is a tricky one, might need your input. Although I expect the answer is "this is not supported"

[hpkfft]

See also: #1067, #1195, and the files tests/*inter_module*

[dograt]

Can confirm that this just works. Thanks!