search for: libvoip

Hi everyone, In the 1.1.x branch, I've kept adding more stuff to libspeex: preprocessor, AEC, etc. I'm now considering moving all those to a separate library (libvoip, libspeech, whatever). Anyone on this list has good reasons I should consider for either splitting or not splitting libspeex? Cheers, Jean-Marc

...sday, June 28, 2006 2:55 AM To: Jean-Marc Valin Cc: speex Subject: Re: [Speex-dev] Library split (poll) Jean-Marc Valin wrote: > In the 1.1.x branch, I've kept adding more stuff to libspeex: > preprocessor, AEC, etc. I'm now considering moving all those to a > separate library (libvoip, libspeech, whatever). Anyone on this list > has good reasons I should consider for either splitting or not > splitting libspeex? I'd argue for a separate library; in space-constrained environments, it would be good to be able to easily not include these additional features. Gerv ____...

...c Valin > Cc: speex > Subject: Re: [Speex-dev] Library split (poll) > > > Jean-Marc Valin wrote: > > In the 1.1.x branch, I've kept adding more stuff to libspeex: > > preprocessor, AEC, etc. I'm now considering moving all those to a > > separate library (libvoip, libspeech, whatever). Anyone on this list > > has good reasons I should consider for either splitting or not > > splitting libspeex? > > I'd argue for a separate library; in space-constrained environments, it > would be good to be able to easily not include these additi...

...ine.LNX.4.62.0606291652150.30841@mix.hive.no> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > Hi everyone, > > In the 1.1.x branch, I've kept adding more stuff to libspeex: > preprocessor, AEC, etc. I'm now considering moving all those to a > separate library (libvoip, libspeech, whatever). Anyone on this > list has > good reasons I should consider for either splitting or not splitting > libspeex? I'd much prefer it if it was still just one library. At the moment, I bundle the library with my Win32 applications (and one file is better than 3),...