In this case, we should consider using the ‘Windows’ base image, which has a complete set of APIs. However, it’s a shame that the Windows Version of FFMPEG requires desktop APIs to run its function, and the server core container image does not have the APIs. You may think if the container can handle these multimedia workloads, it will be an excellent service to many users and companies. I can't seem to find the reason why this doesn't statically link ffmpeg.Starting Windows Server 2022, Microsoft has released a new kind of base image called ‘WindowsServer.’ The ‘WindowsServer’ base image is the same as the existing base image called ‘Windows’ but designed for the Windows Server-specific feature sets and its release cadence.įFmpeg is a cross-platform multimedia transcoding software that can handle various audio, video, and image formats.

rlib file, that ffmpeg-next should in turn be able to statically link correctly. The important part seem to be there: the rust-ffmpeg-sys crate is compiled with -l static=avcodec -l static=avdevice -l static=avfilter -l static=avformat -l static=avutil -lĪnd the path to the lib is correct: -L native=/home/polochon/Documents/Programming/Rust/bliss-rs/ffmpeg/lib.

What bugs me is that looking at the rustc execution, it seems that it should work (pasted on an external website because it's huge Past-isserie). The compilation process works flawlessly, but then I get errors such as 0158:err:module:import_dll Library avcodec-59.dll (which is needed by L'Z:\path\to\metadata.exe') not found, which pretty explicitly means that the static linking failed.ĬARGO_FEATURE_STATIC=foo FFMPEG_DIR=/path/to/precompiled/ffmpeg/windows/ffmpeg cargo build -release -example=metadata -target x86_64-pc-windows-gnu -verbose -features=static I'm trying to cross-compile a rust-ffmpeg example from linux x86_64 to x86_64-pc-windows-gnu, and then execute it.

Ffmpeg for windows binaries