Hunk #2 succeeded at 244 (offset 5 lines).Ĭonfiguring ffmpeg_git_pre_x264_with_fdk_aac (/home/USER/ffmpeg/ffmpeg-windows-build-helpers/sandbox/win64/ffmpeg_git_pre_x264_with_fdk_aac) as $ PKG_CONFIG_PATH=/home/USER/ffmpeg/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/x86_64-w64-mingw32/lib/pkgconfig PATH=/home/USER/ffmpeg/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/bin:$PATH.
CONFIGURE FFMPEG WINDOWS PATCH
% Total % Received % Xferd Average Speed Time Time Time Currentġ00 14 0 0 1396k 0 -:-:-:-:-:-:- 1396kĪpplying patch frei0r_load-shared-libraries-dynamically.diff
CONFIGURE FFMPEG WINDOWS CODE
Your branch is up to date with 'origin/master'.įetched no code changes, not forcing reconfigure for that. building of FFmpeg extra codecs, like libvpxĪnyway, you can try adding some "experimental" build option (like OPENCV_FFMPEG_WIN32_NATIVE) to allow find_package(FFMPEG) or similar (but perhaps we would not try testing this, so this workaround should not be large to prevent dropping of them).Done git cloning to ffmpeg_git_pre_x264_with_fdk_aac.control FFmpeg build flags, don't allow GPL-only components.You can built your own OpenCV FFmpeg wrapper via Docker (Ubuntu 16.04) from scripts here: (whole repository is large, consider cloning only required branches/commits: -b ffmpeg/master -depth=1)Ĭurrent OpenCV wrapper build process also resolves this: Second reason: "external" FFmpeg API is not very stable and there is no way to guarantee work with custom FFmpeg prebuilt versions (OpenCV's FFmpeg wrapper has fixed FFmpeg version and it is tested before integration into OpenCV).
So OpenCV can't be linked FFmpeg library directly.
CONFIGURE FFMPEG WINDOWS LICENSE
The first reason for this is license conflict:
0 kommentar(er)
