similar to: VS2005 build stability?

If you remove the project files, I doubt it's going to make things easier for anyone. You'll probably just increase the number of questions as people struggle to compile using less common and less user-friendly methods, and someone is going to have to maintain that anyway. VS users want VS project files. Plenty of open-source projects provide them. It's not that hard.

On Fri, Oct 3, 2008 at 7:15 AM, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > David Hogan a ?crit : >> That said, we don't use the supplied project. We simply compile in >> the speex .c files. You could easily replace the Win32 build files >> with a readme showing which .c files NOT include in your project >> file. >> >> If you'd

Might I make a suggestion? I manage a few rather large cross platform projects which include embedded targets, Windows OS w/ multiple Visual Studio targets (2003, 2005, and 2008), and some Linux flavors. In the past we hand built all the makefiles and manually maintained the Visual Studio project / solution files, which has always been a pain. Recently we've made a successful partial

I am trying to build 1.2beta1. I downloaded the sources from http://downloads.us.xiph.org/releases/speex/speex-1.2beta1.tar.gz and tried compiling it under visual studio 2005. it gave the following errors: LIB : fatal error LNK1181: cannot open input file '.\debug_rtl_dll\medfilter.obj' Build log was saved at

On Thu, Oct 2, 2008 at 12:07 AM, Jean-Marc Valin < jean-marc.valin at usherbrooke.ca> wrote: > Tom Grandgent a ?crit : > > If you remove the project files, I doubt it's going to make things easier > > for anyone. You'll probably just increase the number of questions as > > people struggle to compile using less common and less user-friendly > > methods,

Hi, Is is possible to have makefiles, batchfiles, whatever that just calls the command-line compilers and doesn't require this huge amount of per-compiler-version crap? Otherwise, I'm seriously considering removing all those project files from the build since time has proven there's just no way to get them up-to-date. Jean-Marc Alexander Chemeris a ?crit : > Hello, > > On

Please note that I'm not advocating CMake as a replacement for autotools or another build environment - what I was postulating is that CMake may provide an easier to maintain option for generation of Visual Studio project and solution files, which unless I'm mistaken the GNU autotools suite does not support. Used in this manner they provide the ability to generate these for at least

Hi, I use the pre-compiled libs of speex, version beta3. I've got this link problem when I use the fonction speex_encoder_init(&speex_wb_mode) error LNK2001: unresolved external symbol _speex_wb_mode I made the link with the librairies libspeex.lib and libspeexdsp.lib in my properties' project. I used the dumpbin executable of VC to see the external variable defined in the libs,

Hello, On Wed, Oct 1, 2008 at 8:29 PM, Kerry Bonin <kerry at vscape.com> wrote: > - Anyone else see this? > - Who maintains the Win32 projects (at least the VS2005)? I'd be happy > to work with to solve. > - If nobody is actively maintaining this build, I'd be glad to fix and > contribute back. I'm currently listed as a Win32 build system maintainer, but I

Hi I downloaded speex-1.2beta2 from svn.xiph.org/releases/speex and am trying to build the win32/VS2005/libspeex/lipspeex.vcproj When I try to build the Release configuration, I get the following error: LNK1181: cannot open input file '.\Release\medfilter.obj' Trying to build the Debug or Release_Dynamic configurations gives a related error: C1083: cannot open source file:

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Jean-Marc, Frank, I have stumbled across a similar situation regarding optimization. I seem to have a similar setup as Frank does with a fixed 48khz in and out. The wideband mode and ultra-wideband modes are really what I?m looking for. I have a test application that reads audio, downsample to 16kHz (or 32kHz), speex encode, speex decode, upsample back to 48kHz, and playback. If I remove

Tom Grandgent a ?crit : > If you remove the project files, I doubt it's going to make things easier > for anyone. You'll probably just increase the number of questions as > people struggle to compile using less common and less user-friendly > methods, and someone is going to have to maintain that anyway. And how is having out-of-date project files help. > VS users want

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

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

David Hogan a ?crit : > That said, we don't use the supplied project. We simply compile in > the speex .c files. You could easily replace the Win32 build files > with a readme showing which .c files NOT include in your project > file. > > If you'd like, I'd be happy to produce a readme file on how to make a > VC project file for speex. Although this approach would

Hi Jean-Marc, after some problems with getting svn to work here I finally made it. Problem is, you write that I cannot use libspeex and libspeexdsp at the same time now -- because I use a "live" system (mic-in -> speex_enc -> speex_dec -> headphone out) and I can run the AD1836 audio codec on 48 kHz only, I cannot use my program now (because I use speex resampling...) So I

Hello. I'm having problems with the dynamic library of libspeex under win32. I have used the static library for a while with no problems. When I try to compile my application with the dynamic library I get the following link error: codec_speex.obj : error LNK2001: unresolved external symbol _speex_uwb_mode codec_speex.obj : error LNK2001: unresolved external symbol _speex_wb_mode

When built with --with-fft=gpl-fftw3, libspeexdsp is not linked with libfftw3, while it uses symbols from it. This means every object linked with libspeexdsp should also be linked with libfftw3, but it is not something reflected in the pkgconfig file. Instead, link libspeexdsp with libfftw3 when --with-fft=gpl-fftw3, and remove explicit link with libfftw3 in objects build by the speex Makefile.

This patch enables compilation with GCC 4.7.1 and --enable-shared=yes --enable-static=no --enable-vorbis-psy -------------- next part -------------- diff -r -u speex/configure.ac speex/configure.ac --- speex/configure.ac 2013-04-24 19:08:00.710564608 +0400 +++ speex/configure.ac 2013-04-24 20:04:33.589310544 +0400 @@ -204,7 +204,7 @@ AC_DEFINE([TI_C55X], , [Enable support for TI C55X DSP])