[Ffmpeg-devel] Re: FFMPEG on Windows
Wed Aug 31 11:10:29 CEST 2005
Marcus Engene said:
> Martin Boehme wrote:
>> If it is the former are you experiencing a performance increase over
>> Compiling FFmpeg itself under MSVC would be a huge porting fest, and
>> unless you wanted to take a big performance _hit_, you'd have to
>> convert large chunks of inline assembler from AT&T syntax to Intel
> Couldn't the asm things be wrapped in macros? How do other multi
> platform projects deal with this?
Some put the assembler bits in separate files, and use nasm or some other
> I agree that MS isn't really run by mother Theresa, but Visual Studio
> beats the hell out of any other ide I've worked with.
In terms of being irritating, yes.
> And yes, I tried the marvels of programming with emacs/gcc and I didn't
> like it. gdb or ddd are beaten by the VS debugger hands down, imho.
Load a project in VS, set some breakpoints, and start the thing running.
Then switch to some other window and try to do something else while
waiting for the breakpoint to be reached. Finally, realize that you
can't do a thing, because VS has frozen the entire machine solid. This
is under Windows XP Pro SP2 with 1GB RAM and 3GHz clock. (Why oh why
do they make use use this stuff at work?)
> Most incompatible (C99?) examples I've seen VS fail with on this list
> are irrelevant cosmetics (apart from lack of inttypes.h), as far as I
> could tell. imho again ;-)
C99 struct initializers are all but cosmetic. They are very useful when
only some of the fields need to be initialized, and you don't need to
remember the order of the fields either.
All this IMNSHO.
mru at mru.ath.cx
More information about the ffmpeg-devel