A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://ffmpeg.org/pipermail/ffmpeg-devel/2007-January/028256.html below:

[Ffmpeg-devel] [PATCH] Partial port of ffmpeg to MS Visual C

[Ffmpeg-devel] [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issue [Ffmpeg-devel] [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issueDiego Biurrun diego
Tue Jan 30 11:28:09 CET 2007
On Tue, Jan 30, 2007 at 09:25:38AM +0100, Steve Lhomme wrote:
> Michael Niedermayer wrote:
> >
> >On Mon, Jan 29, 2007 at 10:15:00AM +0100, Steve Lhomme wrote:
> >>
> >>Anyway, C99 doesn't cover inline ASM AFAIK so you can't seriously say 
> >>that FFMPEG is not designed for gcc.
> >
> >you know very well that they are under #ifdefs (some of the other people
> >who claimed that ffmpeg where written for gcc may or may not have known 
> >that but you do as you have worked with the code)
> 
> 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.

Why exactly are the #ifdefs not clean?  It's much cleaner to control
conditional compilation from the build system instead of using the
preprocessor.

Diego



More information about the ffmpeg-devel mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4