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

Michael Niedermayer michaelni
Sun Dec 3 17:11:27 CET 2006


On Sun, Dec 03, 2006 at 02:41:28PM +0200, Uoti Urpala wrote:
> 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.

as these arent supposed to be vissible to the outside you can never have a
problem with headers from 2 projects ...


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is

More information about the ffmpeg-devel mailing list