summaryrefslogtreecommitdiff
path: root/doc/general.texi
diff options
context:
space:
mode:
authorStephen Hutchinson <qyot27@gmail.com>2019-03-31 20:12:55 -0400
committerGyan Doshi <ffmpeg@gyani.pro>2019-05-04 12:01:58 +0530
commitd19f8e711c06287006e680c1bd417ffe52074a6b (patch)
tree29e651076315e97b3e6314908c416a951d416630 /doc/general.texi
parent55895df4c8bf0ed9cdaa3b8c638e51ac920180ae (diff)
doc/general.texi: add note about 32-bit GCC builds of AviSynth+
Diffstat (limited to 'doc/general.texi')
-rw-r--r--doc/general.texi15
1 files changed, 15 insertions, 0 deletions
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
+@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.
+@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