"MSVC works fine! Just go to MSYS2 first"
That isn't "working", that's a horrible workaround. Not to mention this
is a nightmare to script or run in a CI environment.
Again, *I have tried this and it isn't good.* It's very prone to
breaking and pretty much impossible to make any meaningful changes. Not
to mention it almost never works
> Porting everything to any other build system without causing an
endless slew of regressions and dropping support for a ton of targets is
virtually impossible.
Call me crazy but I don't think FFmpeg needs to support somebody's 2003
toaster running a 200 MHz POWER4. Everything else is trivial to keep
support for, because *CMake literally runs everywhere.* See
https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_NAME.html.
On 1/23/26 9:49 PM, Timo Rothenpieler via ffmpeg-devel wrote:
That's very unlikely to happen.
The current scripts support building using msvc just fine.
Porting everything to any other build system without causing an
endless slew of regressions and dropping support for a ton of targets
is virtually impossible.
Just open a MSVC command prompt, launch C:/MSYS64/msys2.exe (or
wherever you installed it) or if you got it set up wsl.exe, run
./configure --toolchain=msvc and build away.
Timo
_______________________________________________
ffmpeg-devel mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
