[FFmpeg-devel] On in-tree external headers

Carl Eugen Hoyos ceffmpeg at gmail.com
Wed Nov 1 01:52:54 EET 2017

2017-10-31 17:52 GMT+01:00 Mark Thompson <sw at jkqxz.net>:
> On 31/10/17 16:34, Timo Rothenpieler wrote:

>> We're not bundling entire 3rd party libs in-tree here, just
>> API headers for system/driver APIs.
> What exactly would the policy be, then?
> "External headers for a system/driver API may be included in tree
> if it makes building with support for this feature easier for users"
> would cover pretty much everything.
> I'm definitely against a free-for-all where libmfx, V4L2, etc. all
> get included.

Could you elaborate? I apparently miss something.
Why would anybody want to put a libmfx or v4l2 header into the
FFmpeg codebase?

Carl Eugen

More information about the ffmpeg-devel mailing list