

The slowest thing is forking emulating it in Win32 executables is not easy on NT kernel. (I recommend Cygwin, I've been using it for 15 years or so, and have access to almost everything I've ever needed from Linux command line.

MSYS2 doesn't try to duplicate Cygwin's efforts more than necessary, so the number of provided POSIX-emulated software is very small. without requiring a POSIX emulation layer). The shell and core tools exist mainly to allow porting Unix programs to run natively on Windows (i.e. MSYS2 provies a minimal shell required to run autotools and other build systems which get the source for software from the Internet from different repositories, configure them and build them.

# Create CMD scripts for FFmpeg and FFprobeĮcho "* Creating CMD scripts for FFmpeg and FFprobe "Įcho 'set run_binary="%~d0%~p0\bin\ffmpeg.According to the MSYS2 devs, MSYS2 is slightly slower than Cygwin, and it has a significantly different project objective, leading to much reduced command-line environment:Īs for whether it's slower, I expect there'd be very little difference but MSYS2 would be a tiny amount slower due to the extra conversion work. configure -prefix=/usr -enable-static -disable-opencl -disable-cli If thenĬp -rfv /usr/include/w32api/strsafe.h /usr/include/w32api/strsafe.h.bckĬp -rfv cygwin_fix_strsafe.h /usr/include/w32api/strsafe.hĬp -rfv cygwin_fix_strsafe.h /usr/include/w32api/strsafe.h_fix
