[vlc-devel] [vlc-commits] Simplify V4L2 configure checks

Rémi Denis-Courmont remi at remlab.net
Mon Sep 5 23:14:00 CEST 2011

Le lundi 5 septembre 2011 20:36:36 Alexis Ballier, vous avez écrit :
> On Mon,  5 Sep 2011 18:19:01 +0200 (CEST)
> git at videolan.org (Rémi Denis-Courmont) wrote:
> > vlc | branch: master | Rémi Denis-Courmont <remi at remlab.net> | Mon
> > Sep  5 18:26:52 2011 +0300|
> > [812b6e27ce3f4ed84ce547dc2365b844931729d8] | committer: Rémi
> > Denis-Courmont
> > 
> > Simplify V4L2 configure checks
> [...]
> >  - remove mostly useless --enable-libv4l2 and --enable-v4l2.
> well, --enable's are indeed mostly useless, but --disable's, which
> were also removed here, are as useful as the dozens of other ones:

--disable is mostly useful to disable large beasts pieces like skins2, or fail 
if not found dependencies like avcodec.

There is no point for v4l2 which depends on nothing other than libc headers. 
If you want to argue about v4l2, then why do you not argue about every other 
plug-in that is always enabled?

> they allow to forcefully disable {lib,}v4l2 support even if I have libv4l
> installed, or the v4l headers,

You could do it. So what? If you don't want v4l2, don't install the plug-in, 
just like you have to do with the gazillions other automatically plug-ins.

And by the way, when FB and DVB went fully automatic nobody complained.

> so that, whatever extra stuff is installed on my (build) machine,
> it doesn't change what plugins I will have and what not,
> granted ./configure is fed with the right options.

Compiling VLC without libc is not supported and never was. I don't see where 
you're going.

And there are too many configure options. You're not helping people compile 
VLC from scratch so often, are you?

Rémi Denis-Courmont

More information about the vlc-devel mailing list