This means that Debian and its variants won't have an FFmpeg that can use AviSynth+ OOTB. The only two ways to work around this would be either to get an avisynthplus package sponsored in Debian straight-away, at which point it could be re-enabled in the FFmpeg over there, or to add an FFmpeg package here that provides one configured with --enable-avisynth. Barring just having Debian apply a patch that adds the headers back into compat/, but that's a bit ugly.
I know I'd like to see an avisynthplus package accepted into the main distro repositories (especially given all the software that depends on FFmpeg where this would be a boon, like mpv and kdenlive), but if that doesn't happen, then there should be some way for users that don't want to build FFmpeg from source to get up and running with one that can use AviSynth+.
So unfortunately, Debian changed its FFmpeg configuration to drop
--enable-avisynth
since the headers were removed from compat/. Calling the headers 'embedded code' is a little odd, but I guess technically correct?This means that Debian and its variants won't have an FFmpeg that can use AviSynth+ OOTB. The only two ways to work around this would be either to get an avisynthplus package sponsored in Debian straight-away, at which point it could be re-enabled in the FFmpeg over there, or to add an FFmpeg package here that provides one configured with
--enable-avisynth
. Barring just having Debian apply a patch that adds the headers back into compat/, but that's a bit ugly.I know I'd like to see an avisynthplus package accepted into the main distro repositories (especially given all the software that depends on FFmpeg where this would be a boon, like mpv and kdenlive), but if that doesn't happen, then there should be some way for users that don't want to build FFmpeg from source to get up and running with one that can use AviSynth+.