[Ffmpeg-devel] libavutil conflict with system headers on Darwin

Uoti Urpala uoti.urpala
Sun Dec 3 13:41:28 CET 2006

On Sun, 2006-12-03 at 12:34 +0100, Michael Niedermayer wrote:
> > The things in question are symbols with external linkage
> > and preprocessor macros visible to apps using lav* or are defined
> > before system headers are included when building ffmpeg.
> no, always_inline MAX, ... should not be vissible outside they can be
> redifined to (FF_always_inline, FFMAX, ...) for that and system headers
> should be included before lav* headers all just IMHO

It is usually reasonable to include system headers before ffmpeg
headers, but that's not enough to avoid the problem. Other non-system
headers besides ffmpeg ones can also use __attribute__((always_inline)),
and it's not reasonable to require that ffmpeg headers must be included
after those. It would be impossible to include headers from two projects
with such "must appear last" requirements.

More information about the ffmpeg-devel mailing list