summaryrefslogtreecommitdiff
path: root/doc/general.texi
diff options
context:
space:
mode:
authorStephen Hutchinson <qyot27@gmail.com>2019-03-24 16:29:33 -0400
committerGyan Doshi <ffmpeg@gyani.pro>2019-05-04 11:59:56 +0530
commit224aad3026276064eac77be6a9eae1d85f13f36f (patch)
treed17463c4247f88e7398567c56be2af4837dbb28f /doc/general.texi
parentb1681bad33581bc8a018bc9b6ec02761162240e4 (diff)
doc/general.texi: remove note about regressed AviSynth+ header
It's been fixed both AviSynth+-side and locally.
Diffstat (limited to 'doc/general.texi')
-rw-r--r--doc/general.texi13
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/general.texi b/doc/general.texi
index 109c8c58cc..301cf1088c 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -52,19 +52,6 @@ For Linux and OS X, the supported AviSynth variant is
@url{https://github.com/avxsynth/avxsynth, AvxSynth}.
@float NOTE
-There is currently a regression in AviSynth+'s @code{capi.h} header as of
-October 2016, which interferes with the ability for builds of FFmpeg to use
-MSVC-built binaries of AviSynth. Until this is resolved, you can make sure
-a known good version is installed by checking out a version from before
-the regression occurred:
-
-@code{git clone -b MT git://github.com/AviSynth/AviSynthPlus.git @*
-cd AviSynthPlus @*
-git checkout -b oldheader b4f292b4dbfad149697fb65c6a037bb3810813f9 @*
-make install PREFIX=/install/prefix}
-@end float
-
-@float NOTE
AviSynth and AvxSynth are loaded dynamically. Distributors can build FFmpeg
with @code{--enable-avisynth}, and the binaries will work regardless of the
end user having AviSynth or AvxSynth installed - they'll only need to be