whipper VS rust-bindgen

https://github.com/whipper-team/whipper

https://github.com/thomas-mc-work/most-possible-unattended-r...

Finding a good CD drive to rip them is the first step.

https://flemmingss.com/importing-data-from-discogs-and-other...

IME Discogs had the track data most often.

And obviously rip to flac

I have a music library on my home server that I use mopidy to play via the iris plugin integrated into my home assistant UI. It plays over Snapcast which streams over the network to multiple devices in the home with independent volume control. I can fire up the Snapcast client in my phone to get it going there as well, which does work over vpn if I'm away, though I generally just fire up the files from my phones SD card for out-of-home listening. I recently started using whipper on Linux to extract audio from craigslist cds.

https://mopidy.com/

https://mopidy.com/ext/iris/

https://github.com/badaix/snapcast

https://github.com/whipper-team/whipper

It's a Linux app that does CD Ripping. It runs in command line and can basically be semi automatic. https://github.com/whipper-team/whipper

A drive to read CDs and Whipper (automatic bit-perfect checks, conversion to FLAC, and playlist file creation)

(eg. It's the first listed option for Whipper, which is the closest open-source alternative to Exact Audio Copy and a Python project with a ton of C dependencies... and I say this as someone who dislikes Docker enough that I still went through the hassle of the "Building" section.)

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.