[Speex-dev] Re: Windows Mobile build, memory allocation

illiminable ogg at illiminable.com
Wed Jun 28 01:35:29 PDT 2006

Which version of VS, and which version of Windows Mobile are they for?

There are already build configs for Windows Mobile 5 in the repository 
for all the xiph libraries.

If you have configs for the old PPC's, let me know and/or send me the 
project files and i'll put them in the repository.

There's also a directshow(for Windows Media Player on WM5 devices) 
release just waiting to be tested some more before release for vorbis, 
speex and theora in case you are interested.


Jean-Marc Valin wrote:
> On Wed, 2006-06-28 at 11:34 +0530, Ashhar Farhan wrote:
>> I have sent the visual studio project files that compile the speex
>> client to jean-marc directly (as an attachment), sometime this week, I
>> will also upload the binary builds of static library files to my site
>> www.phonestack.com.
> Actually, Zen (illi on IRC) is the one handling the Windows stuff. I
> can't do anything with that (I've never even compiled Speex on
> Windows). 
>> I am porting our LTP (lightweight telephony protocol) to some embedded
>> systems. I require to run speex in an environment that doesn't support
>> memory allocations. How difficult is it to convert speex_encoder_init
>> and speex_decoder_init to use preallocated memory buffers (presumably
>> passed by the initilisatio functions themselves)?
> All you need to do is override some of the functions in misc.c. You
> should need to touch anything else.
> 	Jean-Marc
>> - farhan
>> - farhan
>> -----Original Message-----
>> From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On
>> Behalf Of Gervase Markham
>> Sent: Wednesday, 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
>> _______________________________________________
>> Speex-dev mailing list
>> Speex-dev at xiph.org http://lists.xiph.org/mailman/listinfo/speex-dev
> _______________________________________________
> Speex-dev mailing list
> Speex-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/speex-dev

More information about the Speex-dev mailing list