Ricardo Constantino

I was half joking. I wasn't going to force suite users to do math.

That's sort of why I added `jo`. It could be used to read options from a JSON when needed, instead of passing it to the script. Or a `source`able .sh.

Maybe the fact that it depends on libavutil means they're thinking of importing it directly into libavformat in the future, when it's a bit less alpha-quality.

You could use Windows File History on the local32/local64 directories to keep a "backup" of previous versions of a library and in case of failures to build, you can usually...

https://github.com/m-ab-s/media-autobuild_suite#custom-patches

It's not the suite that needs to comply with LGPL, it's the people that redistribute binaries compiled using it. But I agree it would be somewhat useful to centralize the...

There's no guarantee that MINGW-packages matches absolutely what they use to build. They might not've built the most recent version of the package, or it might not exist in git...

There's also ffmpeg's (and others? can't remember) flavored build_successful* stuff. See clean_suite() on helper.sh

Sure, as long as it's completely optional, since FFmpeg/mpv don't use it.

There's many linux things that don't really work that well when compiled statically or in mingw. What was the need for gstreamer?