-
Notifications
You must be signed in to change notification settings - Fork 32
Windows Prerequisites
This page lists the tools required to build FFmpegKitNext for Windows.
For build commands, see Building Windows. For Windows build options, see windows.sh.
Windows builds target the native architecture of the Windows host. Only arm64 (aarch64) is supported for now; x86-64 is implemented but not yet tested.
Install MSYS2 and run the build from an MSYS2 shell. On an arm64 Windows host, use the CLANGARM64 environment, which provides the native aarch64-w64-mingw32-clang toolchain.
For a step-by-step setup guide, see MinGW Toolchain.
Nix is not used on Windows: it does not provide a native Windows build toolchain. The compiler and host tools come from MSYS2 instead.
Install the mandatory toolchain and host build tools:
pacman -S --needed ${MINGW_PACKAGE_PREFIX}-clang ${MINGW_PACKAGE_PREFIX}-pkgconf make autoconf \
automake libtool git curl rsync pkg-configRapidJSON and FFmpeg are downloaded by windows.sh when they are not already available locally; no separate installation is required for the normal build flow.
Some optional external libraries have extra host-package requirements. Install these only when enabling the matching library:
-
${MINGW_PACKAGE_PREFIX}-mesonand${MINGW_PACKAGE_PREFIX}-ninjafor Meson based libraries:dav1d,harfbuzz,liblc3andrubberband. -
${MINGW_PACKAGE_PREFIX}-cmakefor CMake based libraries such aslibaom,x265andsrt. -
gperfforlibiconv,fontconfigandgnutls. -
bisonforgnutls. -
gettext-devel(providesautopoint),autogenandgtk-docmay be needed when bootstrappinggnutlsandfontconfigon some hosts. -
nasmforx86-64assembly optimizations;arm64does not use it.
The ${MINGW_PACKAGE_PREFIX}- builds of meson, ninja and cmake are required so they target Windows natively. The remaining tools are only run on the build machine, so their plain MSYS2 packages are fine.
Copyright (c) 2026 FFmpegKitNext
- Status
- Versions
- Changelog
- Project Layout
- Using
- Building
- External Libraries
- Patents
- License