[Ffmpeg-devel] [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issue

Steve Lhomme steve.lhomme
Tue Jan 30 10:26:44 CET 2007

Alexander Strange wrote:
> On Jan 30, 2007, at 3:25 AM, Steve Lhomme wrote:
>> The ASM code is #ifdef'd by the makefile. If you compile the code with 
>> another compiler it will fail because the ifdefs are not clean. I 
>> actually made some changes recently to DrFFMPEG to have both ppc and 
>> i386 ASM compiled in the same project at the same time (to make 
>> universal binaries in XCode) and I had to add some cleaner #ifdef's.
> Perian builds universal ffmpeg binaries without having to touch the 
> source, the exception being overriding -O0 for the files that won't 
> compile with frame pointers enabled. It uses lipo.
> http://trac.perian.org/browser/trunk/createStaticLibs.sh?rev=292
> By the way, gcc 4.3 hasn't solved the h264 problems yet (the register 
> allocator is by far the worst part of gcc still there), but the code 
> generated for the C version of the cabac decoder is nearly as good as 
> the ASM, much better than what earlier versions did.

You're building from command-line in 2 pass, you even call configure 
twice. I'm building inside XCode in 1 pass. I think most developers will 
prefer to develop (not just compile) with XCode than the antique gcc+gdb 
in command-line.


More information about the ffmpeg-devel mailing list