[FFmpeg-devel] [PATCH] Revert "Autodetect libxcb."

[wm4]

On Thu, 5 Feb 2015 22:11:22 +0100
Clément Bœsch <u at pkh.me> wrote:

> On Thu, Feb 05, 2015 at 04:55:37PM +0100, Nicolas George wrote:
> > Le sextidi 16 pluviôse, an CCXXIII, Clement Boesch a écrit :
> > > Linux is not only used by desktop. Debian (for example) might want to
> > > provide a ffmpeg-nox11 (just like vim-nox11),
> > 
> > Well, that means they have to put --disable-libxcb when building ffmpeg-nox
> > instead of having to out --enable-libxcb when building ffmpeg-x. Same
> > difference.
> > 
> > (IMHO, they should be specifying both anyways: never rely on defaults and
> > you never have to worry that defaults may change.)
> > 
> > As long as both the enable and disable explicit option work, the default
> > value does not matter much. And in this particular case, considering xcb
> > like a system library seems more consistent.
> > 
> 
> So after each release, packagers need to check the configure and make sure
> there aren't new libraries that will randomly be linked to, and add new
> flag to make sure it's disabled? They will miss some... Or are you
> suggesting them to use --disable-everything and add every internal
> codec/format/filter/protocol/...? (There is no --disable-every-external
> AFAIK).
> 
> Packagers don't want to pull new random (huge) dependencies. That means
> they enable just what they need, and they add the necessary dependencies
> according to the demand.
> 
> That is the original reason we don't auto-enable external libraries.
> libxcb is not more a "system" lib than libx264 is.
> 
> > Personally, I would like that all libraries support auto-detection, with a
> > "--auto-all" option to configure to enable it for everything.
> 
> That's fine with me as well, but we should stick with the non auto-detect
> behaviour by default. Or in the worst case, allow a
> --disable-every-external or something like this.
> 

And why is vaapi considered a system lib?