rust-bindgen VS cargo-generate

Rust supports two kinds of FFI: calling into Rust from another language; and calling into another language from Rust. Most of the thought and tooling that exists right now is organized around the second kind. For example, bindgen is a popular tool that generates useful Rust wrappers from a C or C++ header file.

I have looked into bindgen, but found that it would not be feasible due to OMPL not having a C API, just C++.

Yes! Are you running LLVM version 16.0.0 or newer, by any chance? I believe this is an issue with some builds of bindgen with newer versions of LLVM. See https://github.com/rust-lang/rust-bindgen/issues/2488

On native, you have to define a C API, probably using a header file. Even if both sides are implemented in Rust, they have to speak that C API (documentation).

Bindgen has some functionality for direct talk to C++ https://github.com/rust-lang/rust-bindgen

I am trying to use rust-bindgen (https://github.com/rust-lang/rust-bindgen) to link a static C library (say `libexample.a`) which is compiled in a separate project with CMake. The `libexample.a` depends on other libraries (for example `libcurl.a`) installed on the system.

It looks like the guy you're replying too was kind of an ass, but I do want to point out for anyone else reading that that's not actually that much of a technical limitation: rust code can natively call C code. The main thing you need is a translation of the C library's header file so rustc knows what C functions and structs exist, and that can be automatically generated with bindgen.

It's quite the different approach, but you could consider using bindgen instead.

Use bindgen or CXX to create Rust bindings for the C or C++ libraries.

cargo-generate: Quickly create Rust projects by using existing Git repositories as templates.

This seems to have a lot of overlap with cargo generate. I'm curious if there are differences you're exploring in philosophy/UX/features/implementation/whatever?

cargo-generate to generate projects according to a template (see cargo-generate)

That must be the connector/payment processor integration template. That's not serde specific, it's cargo-generate.

Tools like yeoman, degit, and cargo generate kept me happy for years. They add basic templating capabilities to the standard git clone but they stop there. You’ll be hard pressed to find tools that go beyond setting up a directory structure.

We would like to simply the next step and use cargo-generate tool to create our Arduino project from a template. Somehow (please, do not ask me why) it requires Perl to compile, so we have to do:

How does backpack compare to [cargo generate](https://github.com/cargo-generate/cargo-generate)? I've been using that one until now, but I haven't used its more advanced features.

Currently, it has two built-in ones for `cargo new` and `cargo init` (--bin and --lib) and there are third-party tools like `cargo generate` which provide for more, but they haven't accepted anything into the main distribution yet.

https://github.com/cargo-generate/cargo-generate