diff mbox series

[FFmpeg-devel,4/5] doc/general.texi: AviSynth+ works on Linux now, AvxSynth is gone.

Message ID 20200311105019.8553-5-qyot27@gmail.com
State New
Headers show
Series Switch from AvxSynth to AviSynth+ on non-Windows | expand

Checks

Context Check Description
andriy/ffmpeg-patchwork fail Make fate failed

Commit Message

Stephen Hutchinson March 11, 2020, 10:50 a.m. UTC 
---
 doc/general.texi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff mbox series

Patch

diff --git a/doc/general.texi b/doc/general.texi
index 87eaad7791..e92de9d954 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -58,8 +58,8 @@  For Windows, supported AviSynth variants are
 @url{http://avisynth.nl, AviSynth 2.6 RC1 or higher} for 32-bit builds and
 @url{http://avisynth.nl/index.php/AviSynth+, AviSynth+ r1718 or higher} for 32-bit and 64-bit builds.
 
-For Linux and OS X, the supported AviSynth variant is
-@url{https://github.com/avxsynth/avxsynth, AvxSynth}.
+For Linux and OS X, the only supported AviSynth variant is
+@url{https://github.com/AviSynth/AviSynthPlus, AviSynth+}, starting with version 3.5.
 
 @float NOTE
 In 2016, AviSynth+ added support for building with GCC. However, due to
@@ -77,9 +77,9 @@  GCC builds of AviSynth+ without any special flags.
 @end float
 
 @float NOTE
-AviSynth and AvxSynth are loaded dynamically.  Distributors can build FFmpeg
+AviSynth(+) is 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
+end user having AviSynth installed - they'll only need to be
 installed to use AviSynth scripts (obviously).
 @end float