opencv-rust VS cross

I never tried it, but the OpenCV bindings might work.

I thought it was going to be unsafe because of how Mat is implemented (more information here). ... I tested it and it should be fine memory-wise. My thought was that the code below was going to be allowed to compile.

There are rust language bindings for opencv. https://github.com/twistedfall/opencv-rust

That would seem to indicate you do not actually have OpenCV installed, then. I'd recommend perhaps following the steps for getting the Windows prerequisites set up that the OpenCV Rust bindings provide in their readme.

I added opencv-rust as a dependency to a project. It makes my builds and even cargo check s really slow. It seems to invoke the build.rs script every time even when just type checking. Is this intentional? Is there any way to avoid this?

What is currently missing from https://github.com/cross-rs/cross ?

Compile to musl using this: https://github.com/cross-rs/cross

But the thing is, we have to manually test every build via Steam anyway. Sometimes weird things happen, and at least playing through some part of the game is IMO necessary. I've spent quite a bit of time trying to use cross for cross compiling, but the rabbit hole when it comes to building dynamic libraries seems to go deeper than I'd like, and ultimately couldn't make this work to work on all combinations of all platforms (i.e. using cross on both linux and windows).

Maybe Cross is something to consider? I don't know how much of a sandbox it is, but it runs Cargo inside a Docker container. It has the same CLI as Cargo, you just have to write cross instead of cargo in the terminal.

Are you using cross? They may have a mipsel container you can use, then just replace the linker (if you even need to).

I wonder if using something like cross-rs would help.

Slightly related project: https://github.com/cross-rs/cross