similar to: thusnelda Visual C Inline Assembly

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

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

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

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.

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__) ||

Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Is there not a later free (as in free beer) version? There are also 2008, 2010 and 2012 versions. VS2012 Express requires Win7 to run (though it can create programs compatible with WinXP). VS2010 Express works on WinXP. It is possible to compile x86-64 programs with it, but it requires Platform SDK (also free). VS2005 and 2008

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

All, The thusnelda encoder rewrite is settling down, so as of r16417 I've replaced trunk/theora in svn with the thusnelda branch. This means you no longer have to do anything special to get the new code. If you have an existing theora checkout, it will just update. You may get a warning about conflicts in CHANGES; just accept the new repository version ('tf' at the prompt, or 'svn

Hi all, Attached is a trivial patch that speeds up encoding for key frame only streams. It skips the motion vector search which is not needed when there are never going to be any delta frames. It was made against thusnelda SVN revision 14589. Tested on Fedora 8 x64_64. -Phil -------------- next part -------------- A non-text attachment was scrubbed... Name:

Keith Kyzivat a ?crit : > Something to look into perhaps is Trolltech's 'qmake' tool. > It fills the role of something like autotools or now defunct imake. I think TrollTech deserves a prize for their accomplishment in making qmake even worse than autotools (I'm using it for something else and wish I wasn't -- Qt itself is fine though). I've heard good things about

I'm pleased to announce the first alpha release of the rewrite of the Xiph.org reference encoder for the Theora video format, codename "Thusnelda". http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.tar.bz2 http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.zip http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.tar.gz Please download one of

I'm pleased to announce the first alpha release of the rewrite of the Xiph.org reference encoder for the Theora video format, codename "Thusnelda". http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.tar.bz2 http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.zip http://downloads.xiph.org/releases/theora/libtheora-1.1alpha1.tar.gz Please download one of

Hi All, I know the Thusnelda is suposed to be experimental and its not complete yet but I was interested in trying it out. I see there is an experimental windows version of ffmpeg2therora that uses the Thusnelda encoder, I am attempting to build a Linux version. Presumably the experimental ffmpeg2theora must work to some extent or they wouldn't both offering it for download. I was wondering

this sample is very blocky, the older version seems to do much better and less blocky video. i'm not sure if my 1.9ghz 1 gb ram is the problem here or the encoder has hicups on this new libtheora 1.1 20090806 (Thusnelda). please advice how to fix this or should i use the older version. this encode was 2 pass with horrible output. http://www.megaupload.com/?d=NDGY0EAL General ID

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

Ben Allison wrote: > Here's another go at it. I only have VS2008 and VS2010 to test with right > now. VS6.0, VS2003 and VS2005 are untested. Thanks for your work on this Ben. > I would recommend using FLAC__uint32 instead of uint32_t to avoid these > small #if _MSC_VER < xxxx things everywhere, although I completely > understand the desire to use C99 types. If we add

Hello, My name is Robin Mar?n and I have some questions about the Theora Codec/project... First of all I don't know if this is the right place to ask but I haven't found any Xiph/Theora forum or something similar... I don't even know if this is the right way of "posting" in mailists... But anyway... I discovered Theora just like a moth ago when the 1st alpha of Thusnelda

Fellow Theora users, For long you have waited for the stable release of the official implementation of everyone's favorite video format. Well, this is its Release Candidate, and you are hereby invited to play around with it as much as you want. Here's what's new since beta3: - Merge x86 assembly for forward DCT from Thusnelda branch. - Update 32 bit MMX with loop filter fix. -

Fellow Theora users, For long you have waited for the stable release of the official implementation of everyone's favorite video format. Well, this is its Release Candidate, and you are hereby invited to play around with it as much as you want. Here's what's new since beta3: - Merge x86 assembly for forward DCT from Thusnelda branch. - Update 32 bit MMX with loop filter fix. -