[FFmpeg-devel] On in-tree external headers

Jan Ekstrom jeebjp at gmail.com
Mon Oct 30 22:16:49 EET 2017

On Mon, Oct 30, 2017 at 9:51 PM, Mark Thompson <sw at jkqxz.net> wrote:
> PPS:
> The position stated above would imply removing the avisynth headers.  Can anyone who uses it comment on what would be required for that?

Avisynth headers are available from the Avisynth SDK that comes with
each installer of Avisynth. The reason why some projects made their
own forks of the header is because of the useful features added during
the (rather long) development phase of the 2.6 release, during which
the GPL exceptions regarding the header were removed. And thus people
re-implemented them basing on the 2.5.8 stable header. Not sure if the
GPL exceptions were re-instated with the final release of Avisynth
2.6, and what is the status with the headers that come with the
Avisynth+ project. In any case, the headers are readily available from
various places.

Otherwise the only difference with the included header would be
Avxsynth compatibility? Which is quite a bit less used than original
Avisynth on wine, or Vapoursynth natively on *nix at this point. It
was one of those things where a company forked an old version of a
project and made it compile on *nix, while most of the plugins etc
were quite Windows-specific. The project still does exist and is
available, though.

Best regards,
Jan Ekström

More information about the ffmpeg-devel mailing list