[FFmpeg-cvslog] doc/general.texi: add note about 32-bit GCC builds of AviSynth+

Stephen Hutchinson git at videolan.org
Sat May 4 09:37:08 EEST 2019

ffmpeg | branch: master | Stephen Hutchinson <qyot27 at gmail.com> | Sun Mar 31 20:12:55 2019 -0400| [d19f8e711c06287006e680c1bd417ffe52074a6b] | committer: Gyan Doshi

doc/general.texi: add note about 32-bit GCC builds of AviSynth+

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=d19f8e711c06287006e680c1bd417ffe52074a6b

 doc/general.texi | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/doc/general.texi b/doc/general.texi
index dd01cafd8d..d2324612c2 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -52,6 +52,21 @@ For Linux and OS X, the supported AviSynth variant is
 @url{https://github.com/avxsynth/avxsynth, AvxSynth}.
 @float NOTE
+In 2016, AviSynth+ added support for building with GCC. However, due to
+the eccentricities of Windows' calling conventions, 32-bit GCC builds
+of AviSynth+ are not compatible with typical 32-bit builds of FFmpeg.
+By default, FFmpeg assumes compatibility with 32-bit MSVC builds of
+AviSynth+ since that is the most widely-used and entrenched build
+configuration.  Users can override this and enable support for 32-bit
+GCC builds of AviSynth+ by passing @code{-DAVSC_WIN32_GCC32} to
+ at code{--extra-cflags} when configuring FFmpeg.
+64-bit builds of FFmpeg are not affected, and can use either MSVC or
+GCC builds of AviSynth+ without any special flags.
+ at end float
+ at 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

More information about the ffmpeg-cvslog mailing list