build: remove aviocontext bytes_read check

This define was always just a stopgap for that two month period (August
2021 - October 2021) where the bytes_read field in ffmpeg was completely
missing. Before that time, it was a private member in a struct (which
mpv used). Afterwards, it officially became public. Fortunately, the
lack of this field never actually made it into a release, so it could
have only possibly affected people building from the master branch.
Since ffmpeg 5.0 came out recently, and it's been plenty of months since
that two month window, we can go ahead and drop this check. This
finishes up the work done in 78cfeee2b93830f2988508a653b508336147b79d.

Sidenote: the cached ffmpeg version in the mingw ci were from that time
period when the bytes_read field was missing. The N in the workflow is
bumped to force a full rebuild and fresh clone of ffmpeg.

1 files changed, 0 insertions, 9 deletions

diff --git a/wscript b/wscript
index 074fe8277e..87a3bd6f65 100644
--- a/wscript
+++ b/wscript
@@ -411,15 +411,6 @@ FFmpeg libraries. Git master is recommended."
         'name': '--libavdevice',
         'desc': 'libavdevice',
         'func': check_pkg_config('libavdevice', '>= 57.0.0'),
-    }, {
-        # The following should be removed in 2022 or if libavformat requirement
-        # is bumped to >= 59.8.100
-        'name': 'ffmpeg-aviocontext-bytes-read',
-        'desc': 'FFmpeg AVIOContext bytes_read statistic field',
-        'deps': 'ffmpeg',
-        'func': check_statement(['libavformat/avio.h'],
-                                '(struct AVIOContext){ 0 }.bytes_read = 7357',
-                                use=['ffmpeg']),
     }
 ]