cglue | cxx | |
---|---|---|
10 | 97 | |
168 | 5,527 | |
- | - | |
5.7 | 9.3 | |
24 days ago | 4 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cglue
-
Any sort of plugin engine with dynamic load ability and any limitations?
Shameless plug - you may want to check out cglue, which lets you mix and match rust versions, and even implement plugins in other languages like C++: https://github.com/h33p/cglue
-
GATs in dynamic traits - CGlue 0.2.12 Release
You can grab CGlue from my GitHub.
-
Plugins in Rust: Wrapping Up
I honestly wouldn't say that much has changed during this year. I do see some progress on new libraries like xlang_abi, safer_ffi or cglue, but it's still too early to know, and existing ones like abi_stable move quite slowly.
-
Designing a Rust -> Rust plugin system
You might wanna take a look at cglue: https://github.com/h33p/cglue
-
Exploring System76's New Rust Based Desktop Environment
Importing Rust is the same process as you'd use to import a C library, but there's a lot of people actively invested in this area so there's likely already automated tooling of some sort. Google uses https://cxx.rs for automating C++ bindings to Rust libraries, and lately there's been experiments like cglue to automate C bindings.
-
CGlue 0.2.4 Is Out For Easier Trait ABI Safety
I'm proud to announce one final CGlue release for this year, the highlight being ability to use layout_checks feature on non-git builds!
-
CGlue 0.2 is out! Dynamically loadable traits in Rust, C and C++
I have just added pre-generated headers, they are now on the repo. Yup, certainly not the cleanest, some whitespaces need fixing, but it wasn't the highest priority as it didn't affect functionality.
-
What are the options of distributing a closed-source library in Rust?
Depending on how big your API surface is (and how trait heavy it is), you may want to look into [shameless_plug] automatically generating it with cglue. That's what we did for memflow. [/shameless_plug] It's goals are not much different from abi_stable (in fact, rather a small subset of it focused on traits), but does create C-compatible code.
-
Plugins in Rust: Diving into Dynamic Loading | nullderef.com
It seems like we are trying to solve roughly the same problems when it comes to loading plugins and keeping it all ABI safe. Might be worth checking out CGlue (full disclosure: it's my project). While I do not have async trait support, it would be a really interesting challenge to tackle. The ultimate goal for the project is to be a dead simple code generator that would even allow to write plugins in C/C++, and I currently have sweeping changes underway to get it there.
cxx
-
Rust is having a positive effect in C/C++
There are cxx and autocxx, what else do you propose to do?
-
Interoperability: Swift’s Super Power
I would like to see a comparison of how this compares to Rust. In terms of interoperability it has Cxx (https://cxx.rs) to offer safe bindings to C++ but also has great support for Android, Linux and many other systems. You don't even need to hack together Windows bindings (as explained in the blog post) because Microsoft offers official bindings (https://crates.io/crates/windows). I'm not sure if I'd call it a superpower if any potential interoperability has to be written to be used (compared to it already being available). Or rather, in comparison to what is interoperability a Swift superpower? Certainly not C++ or C which can be used in a far wider set of targets.
-
Rust Cryptography Should Be Written in Rust
We selected Qt as a cross-platform solution. The C++/Rust interface is the clunkiest and ugliest part of the application, and rather complex because some state is shared between several windows in the GUI and several threads in the backend, and any component might modify that state at any time, and updates have to be transmitted to the other components without introducing inconsistencies. Using cxx [1] helped a little, though.
The project began in 2020, and I'm not sure what I'd choose as a GUI framework today – definitely not Qt Widgets, though.
[1] https://cxx.rs/
-
Link a C static library to rust cargo project
If the build process for the C library isn't too involved I recommend using cxx bridge (https://cxx.rs/) and letting cargo handle the build and linking. cxx basically allows you to describe the bidirectional interface (although it sounds like you only need 1 direction, which is fine too) in Rust code and it provides a "good enough" API for compiling C code inside the build.rs file.
-
ffizz: Build a Beautiful C API in Rust
The tooling for the first kind -- calling Rust from another language -- is a bit less developed, and tends to rely on code generation that doesn't necessarily produce a natural C API. cbindgen, uniffi, cxx, and Diplomat all take this course.
-
Best practices in creating a Rust API for a C++ library? Seeking advice from those who've done it before.
I would like to utilize OMPL's functionality in Rust code, so I want to call into OMPL C++ code somehow in Rust. I've seen two (non-mutually-exclusive) options so far: - rust-cpp, which allows you to write C++ code in Rust within the cpp!() macro. - cxx, which allows you to define both sides of the FFI boundary manually (as opposed to bindgen's automatic generation).
-
Hey Rustaceans! Got a question? Ask here (20/2023)!
I'm not sure how to do this in cxx; issues like https://github.com/dtolnay/cxx/issues/447 suggest that this isn't settled yet?
-
Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved]
I use non-vendored dependencies for the Buck build in https://github.com/dtolnay/cxx.
-
Microsoft is rewriting core Windows libraries in Rust
There's also the cpp and cxx crates for doing C++/Rust interop, but they probably aren't appropriate to use in all cases. The C ABI is definitely the safest way to go unless you're really trying to marry Rust and C++ code bases, not just writing library bindings.
-
How can I use rust libraries in C++
There's also cxx (can't vouch for it personally but it claims to make things a lot easier) https://github.com/dtolnay/cxx
What are some alternatives?
libcosmic - WIP library for COSMIC applications
cbindgen - A project for generating C bindings from Rust code
interoptopus - The polyglot bindings generator for your library (C#, C, Python, …) 🐙
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
memflow - physical memory introspection framework
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
windows-drivers - Windows Drivers for System76 Open Firmware Machines
uniffi-rs - a multi-language bindings generator for rust
rust-cpp - Embed C++ directly inside your rust code!
safer_ffi - Write safer FFI code in Rust without polluting it with unsafe code
ritual - Use C++ libraries from Rust