On 02-05-2019 09:58 PM, Stephen Hutchinson wrote:
On 3/30/2019 7:39 PM, Stephen Hutchinson wrote:
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
Ping #1 for five of the six patches.
Will apply #3, 4 and 5 with #6.
#2 looks okay to me, but I'm not acquainted enowith Avisynth to ok it.
But since you're the maintainer for avisynth.c, do you want me to push
them?
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".
