rustshop VS opencv-rust

I was hoping to have https://github.com/rustshop/rustshop be like that, but I've got a Rust dayjob since then, and I have less time for Rust side projects now.

Many thanks to u/dpc_pw, whose notes on GitHub were my starting point for the flake definition. (I also just realized I unwittingly gave my article an almost-identical title by the time I was done refining it, so I’m more indebted to them than I thought.)

Since docker images are mentioned, I'd like to point out that using musl-linked images is often counterproductive, as docker layers with standard library can be shared between different projects and build versions. https://github.com/rustshop/rustshop/discussions/9

and here is the project in this area that I'm working on

rustshop is an attempt at building a template for developers to help them start their own cloud-based system, without much Ops experience.

https://github.com/twistedfall/opencv-rust makes it evident that they do try to support using a prebuild system-opencv. Maybe it is not correctly recognized?

opencv

The de facto solution for smart image processing is to use a computer vision library, such as opencv, which has experimental rust bindings: https://github.com/twistedfall/opencv-rust

There is an OpenCV bindings crate. This example might be what you're after https://github.com/twistedfall/opencv-rust/blob/master/examples/video_capture.rs

For example, this is the build script of the opencv bindings: https://github.com/twistedfall/opencv-rust/blob/master/build.rs

I’m trying to get around a known build issue—it would be great for it to be fixed upstream, but I don’t have any control over it except for setting OUT_DIR during its compilation.

I've been using https://github.com/twistedfall/opencv-rust a lot lately and it's really fantastic, they've done a great job matching up with how C++ works, so there are definitely good examples out there.

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.