opencv-rust VS imageproc (PistonDevelopers)

opencv

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.

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?

I suggest you have a look at the [imageproc](https://github.com/image-rs/imageproc) crate. Personally, I feel like image processing / manipulation in Rust has a long way to go, though.