Displaying 20 results from an estimated 7000 matches similar to: "How to compile libspeex to .lib"
2004 Aug 06
1
Fatal end of line errors occur when trying to compile libspeex in eVC++ 3.0 or 4.0
Hi all,
I'm trying to create a speex decoder library for Pocket PC platform. I then intend to use this library
within my .NET Compact Framework application. But when I simply try to compile the
libspeex files within my eMbedded Visual C++ environment, I receive
the following error
c:\documents and settings\asheeshv.grapecity\desktop\pocketpcdll\speex\bits.c(367) : fatal error C1010:
2004 Aug 06
1
Libspeex-cygwin-EVC++ 3.0
Hello Carl,
Can you send me libspeex compilated in eVC. And can you describe where and how set the FIXED_POINT flag in eVC.
Thanks you.
Regards.
Rodrigo.
<p>----- Mensaje original -----
De: "Carl Douglas"<CarlD@itouchmobility.com>
Env.: 15/01/04 17:43:43
Para: "speex-dev@xiph.org"<speex-dev@xiph.org>
Asunto: RE: [speex-dev]
2004 Sep 29
1
Ask about arm-asm perfomance
How big is difference between encoding speeds of libspeex compiled with
arm-asm, and without it?
My application is written in EVC++, but there is no inline assembler, so
I have to compile speex without arm-asm.
But I still trying to find a way to use speex with arm-asm under my
EVC++ application.
I tried to compile speex with arm-asm under gcc (arm-wince-pe), but
generated static link
2004 Aug 06
1
status report on the Windows CE (PocketPC) ACM codec
>
> It was essentially my own mistake. After the Embedded C++ IDE crashed
unexpectedly,
> the .lib file was no longer present in the project settings (the project
had not been saved)
> so all the errors I got were caused by a missing .lib reference in the
link stage!
> I had to change my cross compiler target to "arm-wince-pe" because
otherwise the
> object/.lib files
2004 Aug 06
0
Libspeex-cygwin-EVC++ 3.0
I have built the Speex library for Pocket PC using the FIXED_POINT flag in eVC 3. It works fine.
I think the iPAQ 3600 (ARM SA 1110, I think this is a 200mhz cpu), is a bit slow for encoding in realtime. The Speex encode function takes 30+ ms to encode one 20ms sample frame in a debug build. I didn't try the release build with compiler optimization.
The iPAQ 3970 (PXA250, I think this is a
2004 Aug 06
1
Libspeex-cygwin-EVC++ 3.0
Hi all,
As someone knows i'm tring to develop a VoIP application
for my ipaq 3850 (200 Mhz) using speex...
I guessed, for better perfomance, to build libspeex using GCC under linux or cygwin with
--enable-fixed-point and --enable-arm-asm and use the compiled library under Embedded VC++ 3.0.
I don't know if it's possible and only today i started to read something about
cross-compiling
2005 Dec 20
3
CVS compilation and EVC++ 4.0
Hi all,
I'd like you to know i'm not able to build Speex library anymore from CVS
without modfing the code in mdf.c.
This is due to the fact that EVC++ compiler doesn't like memory allocations
in this form:
spx_word16_t w[N];
where N is not a constant.
I know this is not an error for gcc compiler and ANSI standard but it is in
VS2005 and EVC++ 4.0
If someone knows how to compile
2005 Sep 29
2
Compiling libspeex for Blackfin
Hi all,
I'm trying to run speex on the Blackfin processor. I'm not familiar
with programming/compiling/linking at all, but I guess the first thing
I need is libspeex compiled for Blackfin, so that my program can use
the library functions. I've downloaded the source files (version
1.1.10) from www.speex.org and I've been trying to compile libspeex
from within VisualDSP++, but it
2005 Oct 12
2
help using libspeex in win32
Hi all,
i'm going to try to create an app using libspeex (Speex 1.1.10) and Visual
Studio and just have a few questions.
First, what's the difference between libspeex and libspeex_dynamic? Do I
need to include both projects in my new workspace?
Next, how do I enable fixed_point using libspeex? Am I correct in assuming
that an ARM processor would be able to record speech as speex files
2004 Aug 06
1
Project setting for embedded visual c++ 3.0
Hi all,
I'm quite new to Speex and i'm tryng to do a porting of it
for my pocketpc platform....
The encodig time seem to be too hight, i think something goes wrong
putting
--enable-fixed-point
--enable-fixed-point-debug
--enable-arm-asm
in project setting of EVC++ 3.0 (i've got EVC++ 4.0 too)
i do my test with an Ipaq 3850 (206 MHz IntelĀ® Strong ARM 32-bit RISC Processor)
running
2008 Aug 07
1
Linking issues (Visual Studio 2005 and libspeex.lib)
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
2006 Feb 14
2
Updated task list for Speex
Hi everyone,
For all those of you who always wanted to contribute to Speex, but
didn't know what to do, I've just updated the list of things that could
be done on: http://wiki.xiph.org/index.php/Speex
The tasks range from maintaining a FAQ to writing a better perceptual
enhancer. Some of the more complex things listed would even make a good
university project! If you're interested in
2004 Aug 06
4
libspeex/SSE Intrinsics with GCC 3.3.x
When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be
added to the CFLAGS in libspeex/Makefile.
GCC 3.1.1 added a new option "-msse" (see
http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New
Targets and Target Specific Improvements") to enable SSE instructions
within the compiler's output (for appropriate architectures).
Compiling speex on
2004 Aug 06
1
libspeex/SSE Intrinsics with GCC 3.3.x
On Fri, Apr 02, 2004 at 12:33:13AM -0500, Jean-Marc Valin wrote:
> Do you have any sample code for that? Also, how do you tell autoconf to
> append '-msse' without running into problems when CFLAGS is not set (and
> usually defaults to -g -O2, but not always).
Example patch attached. It only tries if the use passes --enable-sse;
testing by target arch as Aron suggested is
2006 Jan 31
2
app_conference(Asterisk) with Speex
Just curious, how does Asterisk pack Speex frames in a packet. AFAIK,
Linphone just sends raw packets, as specified in the RTP draft.
Jean-Marc
Le mardi 31 janvier 2006 ? 10:43 -0500, Steve Kann a ?crit :
> jonathan blais wrote:
> > I'm using Linphone. I tested with Asterisk and Speex only, I created
> > a channel with echo and it worked. It seems to have problem when
>
2004 Aug 06
3
status report on the Windows CE (PocketPC) ACM codec
Christian Buchner wrote:
> Now here is where I have problems and not yet found a solution:
I know very little about this, so take everything that follows with a
large pinch of salt.
> * the function names exported in the .lib created by gcc are not compatible
> with the function name decorations that the VisualC++ embedded linker expects.
Which version of gcc are you using? I know
2010 Feb 11
1
Linking issues (Visual Studio 2005 and libspeex.lib)
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
2005 Oct 04
2
Compiling libspeex for Blackfin
Hi Jean,
First, I would like to thank for the prompt reply.
Basically, what I have to do is to run a speex coder/decoder on a
Blackfin processor, on top of the microC/OS II kernel. I wish I could
use uclinux, since I'm familiar with Linux, but this doesn't depend on
me.
You said that the assembly code is written for gcc, not for
VisualDSP++. Furthermore, in the link you sent me, the
2005 Sep 29
0
Compiling libspeex for Blackfin
Hi,
I think the (small) readme has been accidentally omitted from the
tarball. You can get it at
http://svn.xiph.org/trunk/speex/README.blackfin
Note however that all the assembly is written for gcc, not VisualDSP++.
Jean-Marc
Le jeudi 29 septembre 2005 ? 21:24 +0000, Adriano Vilela Barbosa a
?crit :
> Hi all,
>
> I'm trying to run speex on the Blackfin processor. I'm not
2005 Sep 27
2
Speex ver 1.1.10 decoder problem
OK, that was a stupid error in the le_int prototype. It's fixed in svn
now.
Jean-Marc
Le mercredi 28 septembre 2005 ? 11:53 +1000, Jean-Marc Valin a ?crit :
> OK, it seems like I screwed up the wav header code between 1.1.8 and
> 1.1.9. Everything seems fine (playing to soundcard also works), except
> that the length reported for the wav is too short, which is why it stops
>