Using OpenCV in go

stay go Use in opencv It's still a bit of a hassle , If you are using mac or linux not so bad , stay windows It's more painful .

GoCV The package provides opencv 4.5.4 Support for , The official one click installation script .

about linux and mac System , Just follow the official tutorial , There won't be too many problems . The official installation guide is here ：
https://gocv.io/getting-started/linux/
https://gocv.io/getting-started/macos/

about windows The steps are relatively complicated , It passes through MinGW To compile the , First install MinGW as well as CMake , Direct safety MSYS2 It's fine too , But it's better to be with GoCV The official use is consistent , loading MinGW 7.3.0, Because you can see that the directory has been written dead in its compilation script , If they are inconsistent, it will be more troublesome to change them by yourself . The official installation guide is here ：https://gocv.io/getting-started/windows/

In general, the steps can be described in the official documents , If something goes wrong, the environment is generally not well equipped , It's better to MinGW Under the mingw64\bin The catalog is added to PATH In the environment variables . compile opencv You can change it when you need it GOPATH Next \src\gocv.io\x\gocv Inside win_build_opencv.cmd file , because GitHub Network instability often leads to download failure , You can comment out the two deletion sentences marked in the figure , In case you download files again and again and delete them .


compiled opencv It's a dynamic library . I tried to change the compilation option to compile into a static library , But this is go When compiling the program, you will be prompted that opencv Related libraries , I didn't go into details , Because it's urgent , Just use the dynamic library version directly .

GoCV There's something embarrassing about this bag , Because it links to dynamic libraries , So if you want to package your own program for others , You have to put all the opencv Dynamic libraries are put together with the programs we write , You can't use one less .

stay go It's written inside opencv It's still very comfortable , be relative to c++ go Your grammar is much more flexible .

The following is an example of reading pictures and displaying pictures ：

package main

import (
	"gocv.io/x/gocv"
)

func main() { 
    
	img := gocv.IMRead("avatar.jpg", gocv.IMReadColor)
	window := gocv.NewWindow("Hello")

	window.IMShow(img)
	window.WaitKey(0)
}

After running, a window will pop up to show the picture .

relatively , Function to display pictures （imshow） It's not like c++ It can be written everywhere in , stay GoCV You can only define one first window Then from window call IMShow display picture . and ,window Can only be opened in the main thread , If you open a collaboration program to display, the program will hang up directly .

Apart from this little inconvenience ,GoCV It's still great to use .

---

Welcome to my WeChat official account. Notes on Jiangda