commit | 5a53ed651d8670545aa4923ff228203067215d34 | [log] [tgz] |
---|---|---|
author | Devin Jeanpierre <jeanpierreda@google.com> | Wed Jul 31 14:10:34 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 31 14:11:40 2024 -0700 |
tree | 1ad7c9c0270537943efd7b35fc1dea8a667ecc08 | |
parent | d54739c7afaa004c1c6a0f6a1c768932a145cfc6 [diff] |
Support `char` in public interfaces in `:supported`. This was, as far as I know, an unintentional omission of https://github.com/google/crubit/commit/1dd44144c97223ae7602e0dcfc4e44eca43c2f8e. If it was intentional, well, I didn't document it well enough, so whatever. Certainly there's not much harm in it -- yes, I _do_ want to replace `ffi::c_char` with e.g. an ffi newtype, but that is a separate effort. People need to be able to use `const char*`, and we settled on doing the "obvious" thing, the same as with ordinary `extern "C"` FFI, in the MVP. The error was hidden somewhat by the other issues noted in b/356481403, which caused structs that use `char` to still work as expected. PiperOrigin-RevId: 658137222 Change-Id: Ifd810c693d715ef36622588621b716936a854505
NOTE: Crubit currently expects deep integration with the build system, and is difficult to deploy to environments dissimilar to Google's monorepo. We do not have our tooling set up to accept external contributions at this time.
Crubit is a bidirectional bindings generator for C++ and Rust, with the goal of integrating the C++ and Rust ecosystems.
Support for calling FFI-friendly C++ from Rust is in progress.
Support for calling Rust from C++ will arrive in 2024H2.
Consider the following C++ function:
extern "C" bool IsGreater(int lhs, int rhs);
This function, if present in a header file which is processed by Crubit, becomes callable from Rust as if it were defined as:
pub fn IsGreater(lhs: ffi::c_int, rhs: ffi::c_int) -> bool {...}
Note: There are some temporary restrictions on the API shape. For example, functions that are not extern "C"
, or that accept a type like std::string
, can't be called from Rust directly via Crubit. These restrictions will be relaxed over time.
Here are some resources for getting started with Crubit:
Rust Bindings for C++ Libraries is a detailed walkthrough on how to use C++ from Rust using Crubit.
The examples/cpp/
directory has copy-pastable examples of calling C++ from Rust, together with snapshots of what the generated Rust interface looks like.
$ apt install clang lld bazel $ git clone git@github.com:google/crubit.git $ cd crubit $ bazel build --linkopt=-fuse-ld=/usr/bin/ld.lld //rs_bindings_from_cc:rs_bindings_from_cc_impl
$ git clone https://github.com/llvm/llvm-project $ cd llvm-project $ CC=clang CXX=clang++ cmake -S llvm -B build -DLLVM_ENABLE_PROJECTS='clang' -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=install $ cmake --build build -j $ # wait... $ cmake --install build $ cd ../crubit $ LLVM_INSTALL_PATH=../llvm-project/install bazel build //rs_bindings_from_cc:rs_bindings_from_cc_impl