Compiling the native client ourselves?

[est31]

Right now we are using the native client as it was provided by mozilla. But we should investigate how hard it would be to compile the native client ourselves.

[est31]

Tensorflow requires bazel, which seems to not exist in Debian and its derivatives: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782654

[est31]

IBM Linux doesn't have it either: https://bugzilla.redhat.com/show_bug.cgi?id=1470842

[lissyx]

@est31 As part of the transition work documented, the mozilla/DeepSpeech repo is moving to GitHub Actions, you might be able to re-use bits of it in your case. I saw some people doing cross-repositories workflow for example :)

[est31]

@lissyx thanks for the tip! Is that repo still maintained overall? I'm not sure about its long term future, given that the coqui fork seems to have more people behind it.

[lissyx]

@lissyx thanks for the tip! Is that repo still maintained overall? I'm not sure about its long term future, given that the coqui fork seems to have more people behind it.

Well, there is active ongoing work to move from TaskCluster to GitHub Actions. Future of the repo will depend on people investing themselves on it.