
Since the pkg-config tool can't find where your static lib (.a) files reside, it fails.Ĭompiling ffmpeg-sys-next v4.3.0 (D:\3rdparty\rust-ffmpeg-sys)Įrror: failed to run custom build command for `ffmpeg-sys-next v4.3.0 (D:\3rdpar If it doesn't find it, then it tries to invoke the pkg-config tool. What the build script does is check for the FFMPEG_DIR variable first and find the static libraries pointed by it. If you have a latest version of the compiler, then it may work. Since it doesn't recognize the inline keyword present in the FFMPEG headers, it fails.

I used the rust-gnu toolchain since i have an older VC++ compiler that comes with VS 2013.

These DLLs contain the actual FFMPEG libraries implementation.

Restart shell, if it is open, for it to see the newly created environment variable. This folder should contain examples, include and lib folders.
