(In reply to comment #5)
> Pong.
>
> I am still thinking how to make libv4l2 support optional...
>
Why would you want todo that? libv4l was explicitly designed to be transparent to the application.
With the current patch, libv4l does not get used / linked in to the lowlevel v4l-info, v4l-conf and v4lctl programs, so those are not affected, all the others actually stream data from the cam in one form or the other and thus need libv4l to work with cams which have funky video formats (IOW most of them!!).
> P.S. Could you add autoconf stuff for libv4l2 patch as well?
Why? Its a distro specific patch and we will always want to enable libv4l support, I will take a look at autoconf support when a new upstream is formed and patches need to become non distro specific so that they can be merged upstream.
(In reply to comment #5)
> Pong.
>
> I am still thinking how to make libv4l2 support optional...
>
Why would you want todo that? libv4l was explicitly designed to be transparent to the application.
With the current patch, libv4l does not get used / linked in to the lowlevel v4l-info, v4l-conf and v4lctl programs, so those are not affected, all the others actually stream data from the cam in one form or the other and thus need libv4l to work with cams which have funky video formats (IOW most of them!!).
> P.S. Could you add autoconf stuff for libv4l2 patch as well?
Why? Its a distro specific patch and we will always want to enable libv4l support, I will take a look at autoconf support when a new upstream is formed and patches need to become non distro specific so that they can be merged upstream.