On 3/28/2019 1:03 AM, Gyan wrote:
On 25-03-2019 01:59 AM, Stephen Hutchinson wrote:
It's been fixed both AviSynth+-side and locally.
---
doc/general.texi | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/doc/general.texi b/doc/general.texi
index fe94c40386..6ec52962ff 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -51,19 +51,6 @@ 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
-There is currently a regression in AviSynth+'s @code{capi.h} header
as of
-October 2016, which interferes with the ability for builds of FFmpeg
to use
-MSVC-built binaries of AviSynth. Until this is resolved, you can
make sure
-a known good version is installed by checking out a version from before
-the regression occurred:
This would still be an issue for older versions. Maybe keep the note,
but add a date and revision range for the affected versions.
Older versions of what? FFmpeg relies only on the copies of the headers
in compat/avisynth, and with the patch to update the headers¹, we move
directly from unaffected version to unaffected version. The problem in
the header doesn't actually affect AviSynth itself, it affects client
programs that talk to it; the difference in behavior due to Windows'
32-bit calling conventions is explained in a new note in the patchset².
That note about checking out the correct version of the header never
actually mattered to FFmpeg, it was brought in from merging commits from
Libav (which is still affected by this situation, because they don't
provide copies of the right headers in compat/).
¹http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241503.html
²http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241505.html
_______________________________________________
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".
