[Example Request]: How to integrate 2+ cxx crate about corrosion HOT 2 OPEN

I've read that this is possible to have multiple cxx rlib, one rust static library that does extern crate thingy.

Until the rlib format is stabilized for external linker consumption, you do need to ensure that only one rust static library is linked into a C/C++ executable. Adding a dummy crate that depends on the crates you are interested in would be a solution and could be automated by generating a corresponding Cargo.toml.

As for running cxxbridge: I don't work with C++ myself, but in principle all you need to do is run the cxxbridge command once for every file that needs cxx bindings. A nice solution might be to parse the cargo metadata output of the staticlib crate, and run cxxbridge on every dependency that depends directly on cxx (My assumption is that you only depend on cxx directly when you want bindings for that crate). There is already some parsing of cargo metadata implemented, to determine the version of cxxbridge to use.

For a first test, this dependency parsing could be skipped entirely and just pass the relevant .rs file manually via the FILES parameter. The corrosion_add_cxxbridge function needs to be adapted slightly for this to allow absolute paths, and still place the generated files into sensible directories, but I think the cxxbridge itself doesn't really need to know about the crate name or anything.

Then you have a bunch of .cc and .h files, and if there are no duplicate symbol names, just linking the generated cxx static lib with the rust static lib into your C++ project should hopefully work.

from corrosion.

Ok I see, some hours of exploration/experiment are still needed. I'm still new to rust so I'm not that fluent in all of the ecosystem.
I think I will go the simple way of linking to dynamic libraries which should solve the issues right?

from corrosion.