[nvda] Re: USB eSpeak
- From: James Teh <jamie@xxxxxxxxxxx>
- To: nvda@xxxxxxxxxxxxx
- Date: Tue, 27 Feb 2007 15:08:01 +1000
For now, a simpler option is just to make a cygwin specific Makefile
(Makefile.win32 or the like) which kills all the stuff that isn't
necessary. This might mean adding some conditionals to the code to kill
stuff we can't use.
Jamie
Michael Curran wrote:
I could never get portaudio to function correctly in cygwin. I don't
even think it... no hang on, I think it would compile, but when I tried
running any program that used it it gave some weird error with the
library. I really can't remember, but really, I think the best thing is
to try to compile a native windows version of the ESpeak library, and we
can work out some way of playing the waveforms ourselves.
But, what is most important is that we need to be able to easily compile
the ESpeak library in to a dll so that Python can use it with ctypes (or
we could swig it, but I don't know much about that).
Jonathan, I know you once told me that perhaps we could just use the
espeak sapi5 dll directly. However I had a look at all the functions it
exports and they really are quite cryptic, as it is really supposed to
be used via com.
It would be great if we could compile the ESpeak library under cygwin in
mingw32 mode (as in no depending on cygwin1.dll) but I think to do this
well ESpeak source will need to be cleaned up a bit and perhaps use
autoconf and automake etc so that its much easier to make on various
systems, including cygwin.
I would prefer not to have to use a Visual Studio project, though of
course I understand it was easier to do that for the sapi5 driver since
that is very specific to Windows.
The GNU tools such as automake and autoconf etc do support dlls, and
especially when using libtool it does make things quite a bit easier.
I havn't looked at the source for quite a while, but the last time I
tried to compile just the library, I had to edit the makeFile so it
didn't try linking against portaudio etc.
Perhaps I can have a look at the source again and see how hard it will
be to write some autoconf templates etc, it would be worth it if it
could be done.
Mick
--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To unsubscribe from the list send a blank message to:
nvda-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field.
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvaccess.org/nvda/
Message Archive:
http://www.freelists.org/archives/nvda
- References:
- [nvda] working hungarian language of NVDA
- From: tomi
- [nvda] Re: working hungarian language of NVDA
- From: Josh
- [nvda] Re: working hungarian language of NVDA
- From: Michael Curran
- [nvda] Re: working hungarian language of NVDA
- From: Josh
- [nvda] mouse movement and speech synths [was: working hungarian language of NVDA]
- From: James Teh
- [nvda] USB eSpeak
- From: Jonathan Duddington
- [nvda] Re: USB eSpeak
- From: James Teh
- [nvda] Re: USB eSpeak
- From: Michael Curran
Other related posts:
- » [nvda] USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
- » [nvda] Re: USB eSpeak
But, what is most important is that we need to be able to easily compile the ESpeak library in to a dll so that Python can use it with ctypes (or we could swig it, but I don't know much about that).
Jonathan, I know you once told me that perhaps we could just use the espeak sapi5 dll directly. However I had a look at all the functions it exports and they really are quite cryptic, as it is really supposed to be used via com.
It would be great if we could compile the ESpeak library under cygwin in mingw32 mode (as in no depending on cygwin1.dll) but I think to do this well ESpeak source will need to be cleaned up a bit and perhaps use autoconf and automake etc so that its much easier to make on various systems, including cygwin.
I would prefer not to have to use a Visual Studio project, though of course I understand it was easier to do that for the sapi5 driver since that is very specific to Windows.
The GNU tools such as automake and autoconf etc do support dlls, and especially when using libtool it does make things quite a bit easier.
I havn't looked at the source for quite a while, but the last time I tried to compile just the library, I had to edit the makeFile so it didn't try linking against portaudio etc.
Perhaps I can have a look at the source again and see how hard it will be to write some autoconf templates etc, it would be worth it if it could be done.
Mick
- [nvda] working hungarian language of NVDA
- From: tomi
- [nvda] Re: working hungarian language of NVDA
- From: Josh
- [nvda] Re: working hungarian language of NVDA
- From: Michael Curran
- [nvda] Re: working hungarian language of NVDA
- From: Josh
- [nvda] mouse movement and speech synths [was: working hungarian language of NVDA]
- From: James Teh
- [nvda] USB eSpeak
- From: Jonathan Duddington
- [nvda] Re: USB eSpeak
- From: James Teh
- [nvda] Re: USB eSpeak
- From: Michael Curran