virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-02-09 14:14:39 +02:00
Code Issues Releases Activity

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

Browse Source
This commit is contained in:
Stephen Hutchinson 2019-03-31 20:12:55 -04:00 committed by Gyan Doshi
parent 55895df4c8
commit d19f8e711c
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/general.texi
View File

@ -51,6 +51,21 @@ For Windows, supported AviSynth variants are
For Linux and OS X, the supported AviSynth variant is For Linux and OS X, the supported AviSynth variant is
@url{https://github.com/avxsynth/avxsynth, AvxSynth}. @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 @float NOTE
AviSynth and AvxSynth are loaded dynamically. Distributors can build FFmpeg AviSynth and AvxSynth are loaded dynamically. Distributors can build FFmpeg
with @code{--enable-avisynth}, and the binaries will work regardless of the with @code{--enable-avisynth}, and the binaries will work regardless of the