Pre-compiled espeak-data.zip
Closed this issue · 15 comments
I would like to ask if it is possible to retrieve the pre-compiled espeak-data.zip for Android.
I am having a hard time compiling it on Windows, and I would simply like to test it out if possible.
hi.
i think you can just zip normal nvda espeakdata folder and put into
res/raw before compiling.
only thing which i am not sure, but i don't think it will make some
problems is espeakdata.version file in which i don't understand what
is written.
reece: write your opinions too about that.
My question was because I have this missing
"CheckVoiceData.java->Cannot find symbol variable raw".
The author told me that this was because espeak-data.zip is missing.
I wonder how this would resolve the missing reference, but I wanted to try it out.
Can you provide me your compiled espeak-data.zip?
That would be very nice!
create raw directory in your res directory and put zipped espeakdata from nvda for instance.
then try gradlew build or ant debug or ant release respectively.
i don't know hw to explain else.
sorry, it is paid on google play, and without author permission i don't want to spread the apk. 2 dollars is not a big amount to buy it if you can't compile it yourself.
Hmmm... I just wanted to try it out if my error in Android studio goes away when I have the espeak-data.zip. It seems unlogical to me.
first of all espeakdata.zip without -
secondly, i don't know how android studio works, i was compiling it from commandline with ant.
android update project -p . -s -t
ndk-build
put res/raw/espeakdata.zip
ant debug
i am not familiar with gradle but gradle assembeDebug should work, not sure about that.
otherwise, try to install all deps from official instruction or go to linux and compile here.
The version file is simply a SHA1 hash of the zip file. It is used to check if the espeak data needs updating on the Android device -- it will update if the versions are different.
I am not going to provide a pre-compiled version of the zip file as (a) this varies from espeak to espeak, (b) you can easily recreate this from the espeak-data directory, and (c) adding derivable binary files in source control is not how source control systems work.
The autotools/Makefile build system is designed for Linux and other POSIX systems (which should work with cygwin, etc. although I haven't tested it on those systems). The other build/source files are not changed, so it would be possible to build on Windows (just not via a single automated command) as upstream espeak builds on Windows.
But that is only part of the problem.
I just tried to narrow it down.
One problem that I think that will not be fixed by just providing the zip file is this:
R does not have a raw component.
i am saying, what i did and which results i've got.
if you will only think and do not do anything, nothing will be fixed believe me.
i am saying one more time, put espeakdata.zip into res/raw directory and run build process again.
Yes, sorry. I have spent the entire last week trying to get everything going, and I am exhausted. But I will try it anew when I have recovered. :-)
@beqabeqa473 You have really helped me. I thought R.raw was part of a library.
I did not know that it was a folder!!
Thank you!
did you compile it successfully now?
No, I have not set up Linux in my virtual machine yet, and I don't want to try compiling it on Windows.
But I have created android/res/raw folder, and now "R.raw" is found, so I think it would work.
Right now I only want to understand the logic.
you don't need to create res/raw if you are planning to build it in linux, build system will do everything.
Yes, I only wanted to understand what "R" actually is and where "raw" comes from.
At first, I thought it was a library. :-)