On 11 September 2016 at 01:24, Samuel Thibault <sthiba...@debian.org> wrote:
> Hello, > > Reece Dunn, on Sat 10 Sep 2016 11:35:40 +0100, wrote: > > I have created a 1.49.0 stable release of the current codebase, as well > as a > > 1.0 release of the dependant pcaudiolib project ([2]https://github.com/ > > espeak-ng/pcaudiolib). > > Thanks! > > I'm having an issue, though: ieee80.c doesn't seem to have a free > software licence. > ieee80.c is present in other applications and libraries with similar headers: 1. wxWidgets (extended.c) -- https://github.com/wxWidgets/wxWidgets/blob/master/src/common/extended.c#L20 2. sox (aiff.c) -- https://searchcode.com/codesearch/view/18633063/#l-1043 3. nyquist (ieeecvt.c) -- https://github.com/vijayrudraraju/nyquist/blob/master/snd/ieeecvt.c 4. speech-tools (EST_wave_utils.cc) -- http://www.festvox.org/docs/speech_tools-2.4.0/EST__wave__utils_8cc_source.html#l00626 | Also, release tarballs usually contain ./configure etc., i.e. | autoreconf -i was run before making the tarball, so the user can just | ./configure && make && sudo make install I have included the `autogen.sh` script to generate those files (as used by wayland and various other projects). Thus: ./autogen.sh && ./configure && make && sudo make install I could generate the configure scripts, etc. but they are tied to the version I generate them with (e.g. generating the tarball on testing will make them incompatible with stable and wheezy). | Also, are the generated voice files architecture-dependent? In espeak, | there used to be a difference between little-endian and big-endian | architectures. Yes they are. That should only matter if building the voice files on one architecture for a different architecture. Thus, you need to build the espeak-ng-data for each architecture on that architecture. Let me know if there are problems and I can fix them. Kind regards, Reece
