Update espeak - #11928
Merged
Merged
Conversation
Now using version 1.51-dev commit a4c2ea83c0c072e1227fc7e751ea58a066b52712
michaelDCurran
previously approved these changes
Dec 14, 2020
Commit: "Ported voices from NVSpeechPlayer to espeak variants." Full sha: 82d5b7b04488412845101851f36da6953cac4378F
Contributor
Author
|
Given the extent of the changes in Espeak-ng, the changes to our buildsystem to support it, and given work on speechPlayer in espeak seems like it may still be in process, I'm going to retarget this to alpha (and thus due for release in 2021.1) |
michaelDCurran
approved these changes
Dec 15, 2020
Contributor
Author
|
I have asked for a new release of espeak: espeak-ng/espeak-ng#857 |
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
None
Summary of the issue:
Espeak hasn't been updated in a while. Updating required fixing the build.
During this process it became clear that the build environment was not inheriting the expected settings.
Description of how this pull request fixes the issue:
Testing performed:
Known issues with pull request:
None
Change log entry:
Section: New features, Changes, Bug fixes