wouldn't it be a good idea to have the libraray available as a binary for non-PC platforms like the PocketPC, Symbian and Mac? i am suggesting this as it will allow the developers to go ahead and program to an interface while the development continues. there are builds for symbian, pocket pc and linux already in the tar ball. putting their binaries on the download section will probably give thsoe developing applications around speex the ability to jumpstart. - farhan
I am attaching a library binary build for Windows CE 3.0. libspeex_emce.lib is an x86 emulator build (with debug information) libspeex_armce.lib is an ARMV4 release build This should work well on all the version of Pocket PC including: 1) Pocket PC 2002 2) Pocket PC 2003 3) Smartphone 2002 4) Smartphone 2003 I have tested it on Pocket PC 2003 and Smartphone 2002. Now, i need the gurus to tell me the following: 1) USE_SSE is gcc specific, how do i enable the assembly optimisations for Embedded Visual C compilers? This problem is very realy. The MPx200 (one of my test platforms) runs only at 134MHz. 2) The Symbian systems too run on some of the lower speed systems (esp the Symbian 6.x versions). 3) we need to put a standard api wrapper for a C++ class. Symbian has a rule that not more than 200 bytes on each stack and a limit of the number of stack levels while running Eikon. Does speex comply with that? My own application needs to run speex at 5.9kpbs. Which is the least process intensive way of doing this on PocketPC platform? What should be the API calls made to make it least process intensive? Any voice quality will do (as along as I can recognise the caller's voice) and the bandwidth should be less than 5.9 kbps. - farhan -------------- next part -------------- A non-text attachment was scrubbed... Name: libspeex_emce.lib Type: application/octet-stream Size: 356202 bytes Desc: Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20041112/b02d6500/libspeex_emce-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: libspeex_armce.lib Type: application/octet-stream Size: 328588 bytes Desc: Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20041112/b02d6500/libspeex_armce-0001.obj
Hi all, The symbian port has a problem compiling with mdf.c (probably not a good idea in anycase). Will someone just remove mdf.c from the speex.mmp (the project file) of symbian distribution? - farhan
How about fixing it instead? What's the actual problem with mdf.c? I assume you're using the svn version, which has lots of fixes. Jean-Marc On Tue, 2006-08-01 at 09:52 +0530, Ashhar Farhan wrote:> Hi all, > The symbian port has a problem compiling with mdf.c (probably not a > good idea in anycase). > Will someone just remove mdf.c from the speex.mmp (the project file) of > symbian distribution? > - farhan > > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/speex-dev >
Ashhar Farhan wrote:> The symbian port has a problem compiling with mdf.c (probably not a > good idea in anycase).I just compiled speex from svn (rev 11733) with no warnings/errors, using Series 60 SDK (from 7.0). however I had to fix this small issue: Index: libspeex/misc.h ==================================================================--- libspeex/misc.h (revision 11733) +++ libspeex/misc.h (working copy) @@ -62,7 +62,7 @@ #error I suppose you can have a [ARM4/ARM5E/Blackfin] that has float instructions? #endif #ifdef FIXED_POINT_DEBUG -#error Don't you think enabling fixed-point is a good thing to do if you want to debug that? +#error "Don't you think enabling fixed-point is a good thing to do if you want to debug that?" #endif /alfred