search for: _speex_encode

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

...to change my cross compiler target to "arm-wince-pe" because otherwise the object/.lib files generated by gcc would not be accepted by Microsoft's LINK.EXE. And I got around the leading underscore issue by re-defining all the speex API functions Ugly, but works. #define speex_encode _speex_encode > > *Future conflicts might arise from the 2 different stdlib implementation. > > The gcc code will use the open-source "newlib" while the Visual C++ compiled > > code will rely on Microsoft's libc. > > In general, you have to compile everything with the...