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

2019-05-03 Thread Gyan 



On 02-05-2019 10:00 PM, Stephen Hutchinson wrote:

On 3/31/2019 8:12 PM, Stephen Hutchinson wrote:

---
The text has been updated to reflect that 32-bit builds of FFmpeg
in general don't default to AviSynth+GCC compatibility.
  doc/general.texi | 15 +++
  1 file changed, 15 insertions(+)

diff --git a/doc/general.texi b/doc/general.texi
index bafa1e2ea2..6c1acb517c 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -51,6 +51,21 @@ For Windows, supported AviSynth variants are
  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


Ping #2 for the sixth of the six patches.


Will apply this one tomorrow morning.

Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

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

2019-05-02 Thread Stephen Hutchinson 

On 3/31/2019 8:12 PM, Stephen Hutchinson wrote:

---
The text has been updated to reflect that 32-bit builds of FFmpeg
in general don't default to AviSynth+GCC compatibility.
  doc/general.texi | 15 +++
  1 file changed, 15 insertions(+)

diff --git a/doc/general.texi b/doc/general.texi
index bafa1e2ea2..6c1acb517c 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -51,6 +51,21 @@ For Windows, supported AviSynth variants are
  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


Ping #2 for the sixth of the six patches.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

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

2019-03-31 Thread Stephen Hutchinson 
---
The text has been updated to reflect that 32-bit builds of FFmpeg
in general don't default to AviSynth+GCC compatibility.
 doc/general.texi | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/doc/general.texi b/doc/general.texi
index bafa1e2ea2..6c1acb517c 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -51,6 +51,21 @@ For Windows, supported AviSynth variants are
 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
-- 
2.19.1

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".