search for: sipxmedialib

....so using libtool results in a non-portability warning. This is due to PIC code and non-PIC code intermingling. How can I go about fixing this whilst still using an installed libspeex present on the user's system? The long: I am using autoconf + libtool to generate a codec plugin for speex (sipXmediaLib), and I'm trying to eliminate the libspeex.so shared library dependency -- I'd like to have it all in one package - so all that is needed is to drop a single plugin that is then dlopened by our application to supply support for the speex codec (and other codecs too, but that conversation do...

...d use USE_ALLOCA if you do not use _USE_SSE, etc, etc. You have to dig around for some amount of time to find all such things. Just to indicate my position: 1) MinGW build support is good. It should be there. 2) I _will_ maintain VS6, VS2003 and VS2005 projects for Speex as long as we use Speex in sipXmediaLib. It would be great to have them checked in to Speex repo, if no - we will keep them in our. Reasons - handiness, ability to link statically, support for WinCE. 3) Project files make compilation much easier for people how want Speex to "just work" and want to use svn version (e.g. because...

I am trying to use the speex echo canceler and preprocessor with sipXtapi to develop a sip user agent. the sipXmedialib call flow graph uses 10ms frames and I am not sure what the implications are if I try to change this. The documentation seemed to indicate that a 20ms frame was recomended, but it didn't go into the consquences of using other frame sizes. We are going to use headsets in production but ther...

What's wrong with a plain old .bat file, or even an NMAKE .mak file? Ship two files, debug.bat and release.bat, and call it good. It is best to leave project-file creation up to individual users, in my opinion. MS changes their IDEs and project-file formats more often than most people change their underwear. The odds that any given open-source project will actually compile without any