On 3/10/26 14:48, Varatharajan, Deepesh via lists.openembedded.org wrote: > From: Deepesh Varatharajan <[email protected]> > > Add a recipe for the cxx crate, which provides a safe and efficient > bridge for interoperability between Rust and C++ code. It allows > defining the FFI boundary in a shared Rust module and generates > compatible bindings for both languages during the build process. > > The crate is implemented in Rust and supports zero-overhead FFI with > common Rust and C++ standard library types. > > More information: https://crates.io/crates/cxx > > Signed-off-by: Deepesh Varatharajan <[email protected]> > --- > meta-oe/recipes-devtools/cxx/cxx-crates.inc | 130 ++++++++++++++++++++ > meta-oe/recipes-devtools/cxx/cxx_1.0.194.bb | 34 +++++ > 2 files changed, 164 insertions(+) > create mode 100644 meta-oe/recipes-devtools/cxx/cxx-crates.inc > create mode 100644 meta-oe/recipes-devtools/cxx/cxx_1.0.194.bb >
This is mostly just a thought, I don't intend this as a blocker of this patch. Maybe a loud thought, or a quick-discussion starter? cxx is pretty generic name, I find it hard to guess that it's a Rust library for FFI. Debian prefixes this (and similar packages) with librust - this one is called librust-cxx. Fedora calls it rust-cxx. (Though OpenSuse just calls it cxx - I guess there is accepted no standard) What if we would follow Debian or Fedora naming with such Rust libraries, similar to what is done with many Python and Perl recipes? I imagine that over time there will be more similar recipes.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#125035): https://lists.openembedded.org/g/openembedded-devel/message/125035 Mute This Topic: https://lists.openembedded.org/mt/118240942/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
