cbindgen
RFCs
cbindgen | RFCs | |
---|---|---|
19 | 33 | |
2,205 | 134 | |
1.5% | 0.7% | |
7.8 | 4.2 | |
12 days ago | 11 months ago | |
Rust | ||
Mozilla Public 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.
cbindgen
-
Hello World in Go From Rust
Golang uses cgo to communicate with external C libraries and Rust uses FFI (Foreign function interfaces) to export C functions. Additionally, a library for automatically generating bindings can be used to generate the header files (.h). In our case, we'll only be exporting two C functions, so using cbindgen is overkill but we'll use it regardless because why not? Firstly, we'll write the rust functions we want to export. We'll start by creating a new rust library:
-
Ask HN: Automating multi-lang communication with a meta programming language
[1]: https://github.com/mozilla/cbindgen
-
Nim v2.0 Released
As a 2-step approach, you could also probably use https://github.com/mozilla/cbindgen and then Nim's native C FFI.
-
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.
-
How can I use rust libraries in zig/C
There's also cbindgen for automating the generation of C headers once you've got your code in the right shape and you'll also want to read the Rustonomicon.
-
C Strings and my slow descent to madness
You can backport Rust standard library to C using https://github.com/eqrion/cbindgen .
-
Rust FFI and cbindgen: Integrating Embedded Rust Code in C
Later we'll see what cbindgen essentially does is receive a configuration and a Rust library and then spit out a C header (.h) file. One might think that what cbindgen is doing might not be that special and can be done by hand. In which some cases that might be true if the project is simple enough. Though additionally as the cbindgen documentation states:
-
Nautilus just fucked me. (Gnome paper cuts)
Fuck it, I'll take the bait. Rust allows for amazing C interop by allowing for exporting of C types as a dynamic library, like C. Unlike C, this still allows for Rust's advanced checking at compile time. librsvg is one such library that is being used in the GTK ecosystem that is also almost completely Rust. You can use tools like cbindgen to generate C bindings.
-
Hey Rustaceans! Got a question? Ask here! (47/2022)!
Or alternatively cbindgen to create the header file from the Rust source.
-
7 ways to pass a string between 🦀 Rust and C
The easiest way to obtain the headers for the rust code is to use the cbingen library.
RFCs
- Nim Sum types, 2024 variant
- Nim Roadmap 2024 and Beyond
- Nim v2.0 Released
-
Contribute to the Python-like Nim language
compiler support for object construction shorthand
-
Nim 2.0.0 RC2
Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.
https://github.com/nim-lang/RFCs/issues/477
- please comment on "It totally sounds like the n-word" as well
- Nim goto intermediate representation (NGIR)
-
My Nim Development Weekly Report (3/12)
Following The Roadmap 2023 for community building , you could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.
- Nim Roadmap 2023
-
My Nim Development Weekly Report (2/19)
First of all, the Nim development follows The Roadmap 2023, which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks to be done in 2023. You might subscribe to the roadmap and write down your expectations of Nim in 2023 there.
What are some alternatives?
rust-bindgen - THIS CRATE IS DEPRECATED, please use https://github.com/servo/rust-bindgen.
nimskull - An in development statically typed systems programming language; with sustainability at its core. We, the community of users, maintain it.
cxx - Safe interop between Rust and C++
nimforum - Lightweight alternative to Discourse written in Nim
rusty-cheddar - A Rust crate for automatically generating C header files from Rust source file.
nim-chronos - Chronos - An efficient library for asynchronous programming
flutter_rust_bridge - Flutter/Dart <-> Rust binding generator, feature-rich, but seamless and simple.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
tch-rs - Rust bindings for the C++ api of PyTorch.
shady - Nim to GPU shader language compiler and supporting utilities.
Module Linker - browse modules by clicking directly on "import" statements on GitHub
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at