Open m0nsky opened 3 weeks ago
Thank you for your suggestion.
I don't have in-depth understanding about this licenses. From what I understand: if you had linked your code (statically or dynamically) to GPLv3 library, your code also became GPLv3. Because compiled Unity project is linked to compiled espeak .dll (even if you don't distribute it), I don't think your suggestion would work.
Probably most important, I just want to make sure that people are aware that they are using a GPLv3 compiled library of espeak in their project.
Much better solution would be replacing or removing espeak dependency.
I won't be providing the espeak-ng.dll
library with the game either, I will only bundle piper-phonemize (MIT license) which will have support for epitran in the next version.
I think it would be great to see a separate branch which does not bundle
espeak-ng-data
, so games making use of this package can stay MIT and leave it up to the end user to downloadespeak-ng-data
(or use another phonemizer) to enable optional TTS.