Fixing broken builds and adding README help with installing, building…

[agorman]

…, and running

[agorman]

It would make things a bit cleaner if install and uninstall were added the the Makefile. So that the headers and library files would be recognized by the system. Would you be open to that?

[nshmyrev]

Hello. A big problem is that kaldi build process is very painful and not really manageable for ordinary users. I might accept build from vosk binary module which we distribute in releases. I don't think build from source is reasonable.

[agorman]

I didn't realize I could just download a release with libvosk.so 🤦‍♂️. I can update the README to reflect that rather than suggesting people install from source.

Another problem is the header files. doing a go get github.com/alphacep/vosk-api/go doesn't include the header files. Typically I've seen them included right in the same directory as the go source. I'll continue to look into that tomorrow but let me know if you have any ideas.

[agorman]

Take a look here https://github.com/agorman/govosk

A structure like that allows go get to be used to easily install the module. I don't think storing the .so file there is viable but would it be possible include a copy of the header files in the go directory? If so then the instructions could be to first install a release of vosk. Then just use go get as usual.

[nshmyrev]

would it be possible include a copy of the header files in the go directory?

I'd better add recommendation to download binary package from releases. We will include header file there together with library binary .so file.

I wonder how other popular modules handle this problem.

[agorman]

I'd better add recommendation to download binary package from releases. We will include header file there together with library binary .so file.

That works for me. For now I can just give instructions on what needs to be downloaded and environment variables to use. I'll wait until you have a package with both library and header.

In the future it would be nice to have a way to easily install vosk to the system. Do you have any plans to package vosk (deb, rpm, etc)?

I wonder how other popular modules handle this problem.

I think they assume the required libraries are installed on the system. I use these two libraries.

https://gocv.io/getting-started/linux/ - have OpenCV installed or alternatively follow their process to install it.

https://github.com/Kagami/go-face - assumes you have dlib installed.