Interest in adding experimental Crubit integration

[thunderseethe]

Hello. I work on crubit a tool for C++/Rust interop (in the vein of cxx and bindgen). We're looking to increase support for our tool with build tools outside of bazel. CMake is the strongest contender, and I would like to add CMake support for Crubit by extending Corrosion to expose Crubit generated bindings (I believe Corrosion already does something similar for cxx/bindgen etc.).

Is that something you all would be open to? If so, I'm happy to put together a PR for an experimental feature for it. The biggest change is that our tool allows exposing rust libs, so corrosion would need to generate targets to those libs (rather than just binaries and staticlibs like it does today).

[jschwe]

Could you elaborate a bit on what you mean with exposing libraries?
Is this specifically about shared libraries in the dependency tree, or also about pure rlibs?

[thunderseethe]

This is particular to how Crubit works. It will generate a C++ header for a Rust library (an rlib/rmeta) and then compile them all together into a C++ library. So it would be expanding the generated CMake targets to include library targets (things that produce an rlib) from the Cargo.toml.

[jschwe]

So, first of all I very much appreciate work on improved C++/Rust interop. I'm generally supportive of adding support in Corrosion, if it doesn't have too much impact on maintenance (I don't have much time to work on Corrosion myself these days).

I would like to understand better what kind of build commands would be added, and what the ordering dependencies are.
Corrosion just invokes cargo build under the hood, so we can't really run commands when an rlib is built. Probably this isn't necessary for crubit, but I couldn't find a clear explanation of how crubit generates glue code in the documentation.