Welcome to Linux by Microsoft
Linux for blind general discussion
blinux-list at redhat.com
Fri Dec 15 18:14:45 UTC 2017
Look at this part and tell me if this is cross platform.
"* When you are happy, convert it to a Flite voice.
* Grab the .c and .h files that the Flite voice generation scripts produce.
* You can now use Flite to do your synthesis, and Flite runs on a lot of
different platforms since it is written in portable C.'
And now look at my post here.
'So I decided to try this on my Vinux since it runs Ubuntu 14.04 LTS,
which is what you seem to have, and since it is on a virtual machine, I
could probably do it that way rather than having to pay more to increase
my server's RAM, though I might have to as my web site grows and PHP is
more on demand.'
I have full audio access on my Vinux using VM Workstation. If there
wasn't audio access I wouldn't hear Orca and some of the other sounds.
I heard that the raspberry Pi is something very similar to how you
When I said that it sounded as though I were trying to interpret chinese
was in reference to this.
'Let alone whatever else one might install, e.g. mplayer, irssi, gdb,
etc., etc.' There are some abbreviations I am not familiar with.
On 12/15/2017 10:02 AM, Linux for blind general discussion wrote:
> Building and testing are entirely different things. Getting something
> to work is a further difference, as passing unit tests doesn't even
> mean that the built speech synthesizer will work, especially if it
> can't access an audio device. Think of it this way. You have a
> computer with no keyboard or mouse on it. You can turn it on, and you
> know it runs, either because you can hear the speech or other startup
> sound, or because you can see the screen. You may even be able to
> access a shell and/or some other parts of the OS remotely. You have
> built a typing tutor application, but it only runs locally, and
> there's no way to access it and make it accept input over a network
> connection. Of course the application builds perfectly, and you can
> even say that it passes unit tests. But how do you test it in the real
> world without a keyboard on the machine and no way for it to accept
> remote input?
> And now you have a further complication. Are you trying to build a
> speech synthesizer that runs on Linux, or are you trying to build it
> for Windows? A Linux build will only run on Linux, unless you have a
> cross compiler that can generate Windows compatible machine code. If
> you think I'm speaking Chinese here, do yourself a favor and don't try
> this. If on the other hand you're actually trying to build for Linux,
> you will need a real Linux OS for testing that includes audio output.
> If you are in fact trying to build a Windows compatible speech
> synthesizer, you can't use Linux for that, not even the half-baked
> Linux over Windows solution, because you will need certain Windows
> libraries and subsystems, SAPI for example, that don't run unmodified
> or unemulated on Linux. So it's definitely better to use windows
> development tools on a Windows machine to build for that system, or
> use Linux development tools running on a real Linux operating system
> with an audio device available to build for Linux.
> Imetumwa kutoka nyumba yangu
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list