similar to: 5. Re: how to build libspeex_armce.lib ? (patrick andrieux)

Hi Dave, I tried defining ARM5E_ASM and ARM4_AS, and you are right, it doesn't compile, But I can't say if the problem come from the Microsoft compiler, because if it doesn't know ARM assembly optimizations, who can know ? We may need to include/install something else to use ARM5E_ASM or ARM4_ASM, or maybe this part of speex's code is not finished. I tried to compare both

Hi Dave and JM, I built a .lib for arm architecture. I work on VS2005, and it's actually easy to build. What you have to do is to change the platform on which you want to build your lib. Open the libspeex project in "speex-1.2beta1\win32\VS2005\libspeex" In "Build" menu, choose "Configuration Manager" under "Active solution platform" select

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Could anyone tell me how libspeex_armce.lib Speex 1.1.6 was compiled? (http://www.speex.org/download/libspeex_armce.lib ) Does it exist some modified fixed_arm5e.h for Microsoft EVC arm-asm compiler? or the inline assemlby was compiled with GCC and linked through EVC LINK.exe? if the latter was done could I know how to link with EVC ? Objects

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

Hello Antonio, It was almost a year ago, so I don't remember exactly all what I did, but anyway I'll try to explain to you the main lines. In speex's sources, you should have a specific folder for VS2005 (or VS2003 depending on which Visual Studio you are using), run the project from there. You must compile for arm arch, not i386 arch...you can modify that somewhere in VS. I

Hi list ! I'm Patrick, a french student. i am developping a kind of softphone for pocket PC using speex. Sorry in advance for my bad english. Till now, i had good results, but now i've a problem with encoding. so to summarize, here is a short description of my work : I'm working on pocket pc I'm developing a GUI in C# I'm developing a dll in C++ which use speex

I wish Speex could come with instructions on how to build libspeex_armce.lib. ________________________________ From: speex-dev-bounces@xiph.org on behalf of speex-dev-request@xiph.org Sent: Mon 11/13/2006 3:01 PM To: speex-dev@xiph.org Subject: Speex-dev Digest, Vol 30, Issue 15 Send Speex-dev mailing list submissions to speex-dev@xiph.org To subscribe or unsubscribe via the World

Hi all, i'm using speex under symbian. When i have compiled the lib for ARM platform i have obtained the follow error: "Error: Can not represent OFFSET_IMM8 relocation in this object file format (1)" I have defined FIXED_POINT 1 and ARM4_ASM. The error is in the function forced_pitch_quant contained in ltp.c. The line that produce the error is:

Hi jere, thanks for this link, i'll see if i can do something good with that. speex.dll : ----------- I have a speex.dll which work, and i can encode and decode a wav file. (i used male.wav on speex.org for my test). But my dll is specific to my softphone. In fact i just include speex.h and i call speex functions for [en;de]coding. My code is based on speex website's sample :

I don't know. If that's all it was, why is there a special new property manager to set it? Morten will need to explain what to do in VS2003 to make VS2005 happy. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> The new property manager doesn't exist in VS2003 either. Don't know >> where to add it. > > > Isn't there a place to

On Fri, 27 Jan 2006, Jeff Cohen wrote: > _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in > VS2003. It shouldn't hurt to define it though, even if VC2003 where it does nothing. Right? -Chris > Morten Ofstad wrote: > >> Jeff Cohen wrote: >> >>> The project files need frequent updating. I cannot maintain VS2005 >>>

_CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in VS2003. Morten Ofstad wrote: > Jeff Cohen wrote: > >> The project files need frequent updating. I cannot maintain VS2005 >> project files, so while they could be distributed with LLVM, they >> will become broken fast. Also, VS2003 and VS2005 project and >> solution files cannot coexist in

The project files need frequent updating. I cannot maintain VS2005 project files, so while they could be distributed with LLVM, they will become broken fast. Also, VS2003 and VS2005 project and solution files cannot coexist in the same directories, further complicating matters. Aaron Gray wrote: > Hi Morten, > > If you can make the VS2005 project files availiable on the net then I

OK, it's not that bad - it's even better than before :) The main issue is RWMutex.inc and the use of PSRWLOCK. This requires _WIN32_WINNT to be >= 0x0600, which is not true for VS2005 SP1. Rather than #define _WIN32_WINNT 0x0600 (the file notes that this should build on all Win32 variants), extending the copy/paste of winbase.h to this works fine: #if defined(__MINGW32__) ||

On Fri, 27 Jan 2006, Jeff Cohen wrote: > The new property manager doesn't exist in VS2003 either. Don't know where to > add it. Isn't there a place to add -D_CRT_SECURE_NO_DEPRECATE for the preprocessor? Isn't this all we are talking about, or am I missing something? -Chris >> On Fri, 27 Jan 2006, Jeff Cohen wrote: >> >>> _CRT_SECURE_NO_DEPRECATE

The new property manager doesn't exist in VS2003 either. Don't know where to add it. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it >> in VS2003. > > > It shouldn't hurt to define it though, even if VC2003 where it does > nothing. Right? > > -Chris >

Jeff Cohen wrote: > The project files need frequent updating. I cannot maintain VS2005 > project files, so while they could be distributed with LLVM, they will > become broken fast. Also, VS2003 and VS2005 project and solution files > cannot coexist in the same directories, further complicating matters. The VS2003 project files convert without problems -- you might want to add in

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

In the v7.0 SDK I see _WIN32_WINNT defined in several places: winresrc.h0x0500 if not defined already (Windows 2000) sdkddkver.h0x0601 if not defined already (Windows 7) objbase.hSet based on NTDDI_VERSION, if not defined already objidl.hSimiler to objbase.h sdkddkver.h is included by windows.h in the v7.0 SDK. With SP1 VC2005, it's defined as 0x0500 in only one place (winresrc.h). So it

Hi, what are the goals of VS2005 support for building LLVM? I'm syncing to the v3 branch and while the branch compiles perfectly with VS2008, there are a significant amount of compile errors and warnings with VS2005 SP1 (8.0.50727.867 with KB926601 SP1, to be precise). I also have the latest WSDK installed. A few months back there were only a few minor issues that I managed to clear up.