On 28-03-2019 05:19 PM, Stephen Hutchinson wrote:
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.
Sorry, I assumed, based on the first line, that the validity of the note
was dependent on AviSynth+ code, and hence its version. So, there is no
permutation of ffmpeg master & avisynth+ that can lead to issues with
MSVC builds? If so, LGTM.
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".
