similar to: speex on visual studio 2010

Hey there, I'm having trouble getting speex working with a project that uses it. For some quick background, the game Quake 3 was GPL'ed a while ago. Some programmers decided to throw it into a public svn and improve on it, called it ioquake3. One of the blokes integrated speex into ioquake3 and it works, but I have troubles getting it to compile/link properly with Visual Studio 2005. I

Hi, I've been doing some development for Pocket PC 2003 applications and have happened to chance upon Speex. To date, I've been having some issues in linking libspeex.lib with my application in MS Visual Studio 2005. Upon building my program, I will always receive the error: fatal error LNK1181: cannot open input file 'd:\Recorder\libspeex.lib' Recorder A brief description

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are gone now). The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for

Hi, dear all I got the following problem when using speex1.2beta1 with VS 6.0: LINK : warning LNK4098: defaultlib "LIBCD" conflicts with use of other libs; use /NODEFAULTLIB:library libspeex.lib(sb_celp.obj) : error LNK2001: unresolved external symbol _lpc_window libspeex.lib(nb_celp.obj) : error LNK2001: unresolved external symbol _lpc_window I compiled speex1.2beta1 under win32

The VS2005 project files are known to not be up-to-date, so I can understand that you'd need to fix some things. Can you verify with an import of the VS2003 project files, that there is no need for any fixes, and just works after importing? Managing multiple project files should be minimized if at all possible. If a straight import of vs2003 project files can be done without any changes

Hello, I've been building Clang under Windows 7 and Visual Studio 2008 for a while now, but had not touched it in a few months. Last night I wiped my build tree to do a full rebuild with the latest version, and got the identical error as David Shipman was seeing last September. Are others able to build under VS9 right now? Thanks, John > Subject: Re: [LLVMdev] MS VS2008 build fails -

On Dec 3, 2007 1:24 PM, Stefan Reuther <streu@gmx.de> wrote: > John Miles wrote: > > 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. > > I second that. When I played around

Vijay, I used Code Composer Studio 3.x to directly build everything. There could certainly be issues with the ./configure, make, make install process. There are .pjt files supplied to build in the CCS simulator, so I suggest that you try that. The c55x option is just a compile switch, which deals with the fact that this platform has a 16-bit "byte", among other things. Regards, Jim

I use VS2005/Vista, which works well... Thx, Seung ---- Original message ---- >Date: Wed, 20 Feb 2008 12:02:29 +0800 >From: "Xi Wang" <xi.wang at gmail.com> >Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005? >To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > >Hi there, > >Did anyone try

Dear Nikos, thank you very much for your advice! I am not a little bit new to C++, and experiments (like using another third party library) always turn out to be days of work for me. That is why I would first like to try Speex's new internal resampling function. I am currently still using the old 1.0.4 version. I have now downloaded the new 1.2rc1 version. Unfortunately it does not want

The Opus resampler is actually a bugfixed version of the Speex one. Same interface/API, but with the bugs removed. It's why I recommended it :-) Otherwise I would have recommended something entirely different, like SoXR. On 07/05/13 22:12, Hermann Weber wrote: > Dear Nikos, > > thank you very much for your advice! > > I am not a little bit new to C++, and experiments

I'm not using Opus at all. I'm just including its resampler in my own sources. It's not even a DLL; it's directly compiled together with the rest of my code. You need these sources from the opus-tools package (http://www.opus-codec.org/downloads/): arch.h resample.c resample_sse.h speex_resampler.h stack_alloc.h In your project file, define these macros: #define

Hi Randy, Thanks for reply. I have one question though. While compiling the speex (downloaded from http://downloads.xiph.org/releases/speex/speex-1.2rc1.tar.gz), I gave ./configure -enable-ti-c55x option and then built the library through make and make install using cygwin. In this case, I get this error "error: member "bits.o" of archive

Dear Nikos, thanks! But you use Opus only for resampling, not for entirely replacing Speex, don't you? Greetings! Hermie Am 07.05.2013 22:53, schrieb Nikos Chantziaras: > The Opus resampler is actually a bugfixed version of the Speex one. Same > interface/API, but with the bugs removed. It's why I recommended it :-) > Otherwise I would have recommended something entirely

Something to look into perhaps is Trolltech's 'qmake' tool. It fills the role of something like autotools or now defunct imake. As far as I understand, you can indeed use it for projects that don't do anything with the Qt libraries. Now, it may not have the support for multiple targets that it sounds like are needed for speex, and I know it doesn't have as comprehensive of

can any one provide libspeex.lib compatible to VS 2005 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20100211/14d09af6/attachment.htm

DEAR: I SEEM A BUG FOR speex-1.2rc1.tar.gz ON BUILD IN USING IT. PLEASE LOOK: ===================================================================== make all-recursive make[1]: Entering directory `/tmp/speex-1.2rc1' Making all in libspeex make[2]: Entering directory `/tmp/speex-1.2rc1/libspeex' /bin/sh ../libtool --mode=link gcc -g -O2 -fvisibility=hidden -O3 -msse -o testenc

Actually, it looks like this is already done in Speex as of revision 7150 in SVN (7/15/2004). As long as HAVE_CONFIG_H is defined in the project settings (which it is in all of the project files in SVN), win32\config.h should be included, and this has #define inline __inline in it. Oleg - you should make sure HAVE_CONFIG_H is defined in your project settings. And, you didn't say which

Hello, I maintain audio processing part of code in sipXtapi -- open-source VoIP library. And when I engaged Speex library, I found that its Windows project files are not up to date and use strange settings. They miss several source files and use single-threaded static runtime libraries. I see no benefits of using static and moreover single-threaded libraries. In the modern world very small amount