[FFmpeg-devel] [PATCH 3/5] doc/general.texi: remove note about regressed AviSynth+ header

[Stephen Hutchinson]

On 3/28/2019 11:41 PM, Stephen Hutchinson wrote:
> On 3/28/2019 8:29 AM, Gyan wrote:
>> So, there is no permutation of ffmpeg master & avisynth+ that can 
>> lead to issues with MSVC builds?  If so, LGTM.
>>
> As a test, I tried building FFmpeg with MSVC (which I never do since I 
> always cross-compile from Linux) and --enable-avisynth, and spotted a 
> couple things in the patches I'll need to address, one of which might 
> be better to squash into the header update patch.
I've uploaded the amended 1st patch and added a 6th to deal with the 
issues I encountered when testing the 'build FFmpeg with MSVC' route.  
Since git send-email (or Gmail) screwed up the threading when I sent 
these the first time, this is the proper order:

http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241922.html <-fixed 
header update patch
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241502.html 
<-enabling the additional pix_fmts; nothing has changed on this one
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241507.html 
<-removing the header warning in the docs; nothing has changed on this one
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241504.html 
<-updating the project link to point to the AviSynth wiki page on 
AviSynth+; nothing has changed on this one
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241505.html <-usage 
note about 32-bit GCC builds of AviSynth+ and the AVSC_WIN32_GCC32 
switch; nothing has changed on this one
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241923.html <-new 
(well, technically old) patch to fix FARPROC warnings/build errors