x264 linking error fix, pip3 meson/ninja fix, VapourSynth added, updated libs #246
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
x264 linking error fix
On several different Linux machines I experienced linking errors during building of x264 (symbols defined twice). I traced it down to the
nasm
version. Downgradingnasm
from 2.16.03 to 2.16.01 resolved the issue.pip3 meson/ninja fix
Many Linux distributions (for example Debian, Ubuntu, Linux Mint) have disabled
pip3
for installing packages outside specific python environments, as this could break system packages. The ffmpeg-build-script always tried to runpip3
, even though meson/ninja is installed and this will cause the script to terminate (several issues are opened on this). I changed it, so that meson/ninja is now checked first and only if those commands cannot be found pip3 is used. The script will also display information when trying to use pip3 and inform about the possible error and how this can be resolved by installing meson using the package managerVapourSynth added
VapourSynth is a frame server build around Python and a modern alternative to AviSynth. I enabled the input module in ffmpeg for it. There is no need to build VapourSynth for that, ffmpeg just needs the header files to be able to compile support for it (if a VapourSynth-Script is opened, ffmpeg will load the library (if installed) at runtime)
Updated several libs