StationIapetus VS rust-bindgen

Check Station Iapetus, "commercial project that will eventually be released in Steam".

Besides being clear and easy to use, one of its popular features is the scene editor, which provides a scene preview as demonstrated in this example:

StationIapetus is also big enough.

Thanks! I do have two pretty big games written with the engine - https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rusty-shooter . I've started writing them because it is impossible to get right feature set, without a game that uses it.

Thanks! Huge breaking changes in the API are rare, I'm trying to design the API to be good from the first try. I have three dependent projects, so every breaking change forces me to fix all of those. Usually I need an hour or so to make it compile again, even on large projects like this.

Hello! I've been working on this project for almost 3 months already and it has some decent progress I want to share with the community. The game is about task-force agent sent to the space station to investigate why connection with the station was lost. The plot is incomplete, it is a bit early for writing it entirely, because I'm just "whiteboxing" everything for now, and working on mechanics of the game. Here are the project links: https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rg3d .

Station Iapetus - https://github.com/mrDIMAS/StationIapetus

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.