This was the main reason I wanted to see if I could compile my own FFmpeg binaries. With the help of a third-party cryptography-library (OpenSSL, GnuTLS, or MbedTLS) I could solve that issue. In fact, it was literally my first encounter with Linux (Cygwin) Bash! But after my first attempts I forked Roger Pack's cross-compilation-script and the rest is history. My FFmpeg binaries are compiled with -enable-libfdk-aac, but they don't contain the actual code because of an incompatible license. You can download libfdk-aac separately here and put the dll-file in the same map as 'ffmpeg.exe', or in any map listed in the %PATH%-variable. This was made possible with the help of a patch created by Gianluigi Tiesi. My FFmpeg binaries are also compiled with -enable-frei0r. You can download frei0r video filtering plugins separately here and put the 'frei0r-1' map in the same map as 'ffmpeg.exe'. This was also made possible with the help of a patch created by Gianluigi Tiesi. pkg-config=pkg-config -pkg-config-flags=-staticĭid some more troubleshooting, this is what I found:įirst of all FFMpeg, FFPlay and FFProbe all behave identical, they all display the same error message. My ancient desktop machine has been updated with the PosReady updates as long as they worked, no other software has problems with it. I have two other XP laptops which were not updated with the PosReady updates, and I tried to replace NTDLL.dll on my desktop with older versions of this file from the laptops. No luck, these older versions prevented the desktop computer from booting altogether with a WinLogon error. Then I used DependencyWalker on the desktop testing both the 4 months old build plus the new build. The old build also shows a couple of missing dependencies, but it does work.
I then retrieved the other two XP laptops from the vault and tested the new FFmpeg build there. Both laptops were updated up to the last official XP updates, but no PosReady updates. The first laptop was an old Medion Netbook Akoya E1210 (made by MSI) with an Intel Atom CPU. This time FFmpeg also crashed, but the error message was different.
0 kommentar(er)
