Message ID | 20200324183919.8789-1-qyot27@gmail.com |
---|---|
State | New |
Headers | show |
Series | [FFmpeg-devel] doc/general.texi: AviSynth+ works on Linux now, AvxSynth is gone. | expand |
Context | Check | Description |
---|---|---|
andriy/ffmpeg-patchwork | success | Make fate finished |
On 3/24/2020 2:39 PM, Stephen Hutchinson wrote: > Related to this are the following changes: > * Mention the two methods that AviSynth+ provides for installing > just the headers. > * Expand on users installing AviSynth on their system a little > more. > --- > This is the only patch that needed changes. I'll just ping the > other three. > doc/general.texi | 21 ++++++++++++--------- > 1 file changed, 12 insertions(+), 9 deletions(-) > > diff --git a/doc/general.texi b/doc/general.texi > index 3684847ac1..5f0f1b2ad1 100644 > --- a/doc/general.texi > +++ b/doc/general.texi > @@ -50,16 +50,18 @@ This driver can be installed using amdgpu-pro-install script in official amd dri > @section AviSynth > > FFmpeg can read AviSynth scripts as input. To enable support, pass > -@code{--enable-avisynth} to configure. The correct headers are > -included in compat/avisynth/, which allows the user to enable support > -without needing to search for these headers themselves. > +@code{--enable-avisynth} to configure after installing the headers > +provided by @url{https://github.com/AviSynth/AviSynthPlus, AviSynth+}. > +AviSynth+ can be configured to install only the headers by either > +passing `-DHEADERS_ONLY:bool=on` to the normal CMake-based build > +system, or by using the supplied @code{GNUmakefile}. > > 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, macOS, and BSD, 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,10 +79,11 @@ GCC builds of AviSynth+ without any special flags. > @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 > -installed to use AviSynth scripts (obviously). > +AviSynth(+) is loaded dynamically. Distributors can build FFmpeg > +with @code{--enable-avisynth}, and the binaries will work regardless > +of the end user having AviSynth installed. If/when an end user > +would like to use AviSynth scripts, then they can install AviSynth(+) > +and FFmpeg will be able to find and use it to open scripts. > @end float > > @section Chromaprint > Ping. On Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200324183919.8789-1-qyot27@gmail.com/
diff --git a/doc/general.texi b/doc/general.texi index 3684847ac1..5f0f1b2ad1 100644 --- a/doc/general.texi +++ b/doc/general.texi @@ -50,16 +50,18 @@ This driver can be installed using amdgpu-pro-install script in official amd dri @section AviSynth FFmpeg can read AviSynth scripts as input. To enable support, pass -@code{--enable-avisynth} to configure. The correct headers are -included in compat/avisynth/, which allows the user to enable support -without needing to search for these headers themselves. +@code{--enable-avisynth} to configure after installing the headers +provided by @url{https://github.com/AviSynth/AviSynthPlus, AviSynth+}. +AviSynth+ can be configured to install only the headers by either +passing `-DHEADERS_ONLY:bool=on` to the normal CMake-based build +system, or by using the supplied @code{GNUmakefile}. 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, macOS, and BSD, 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,10 +79,11 @@ GCC builds of AviSynth+ without any special flags. @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 -installed to use AviSynth scripts (obviously). +AviSynth(+) is loaded dynamically. Distributors can build FFmpeg +with @code{--enable-avisynth}, and the binaries will work regardless +of the end user having AviSynth installed. If/when an end user +would like to use AviSynth scripts, then they can install AviSynth(+) +and FFmpeg will be able to find and use it to open scripts. @end float @section Chromaprint