./configure --enable-libvmaf fails to validate vmaf version
All, I have been having difficulty getting libvmaf enabled. I have been getting null results out of older version so I am attempting to rebuild from the latest versions from git. As far as I can tell. pkg-config is recognizing the vmaf package, it is just not validating the version number for libvmaf. Is anyone else seeing this issue? I have tried this both on Mac OS and Windows/MinGW from the latest versions on git. ./configure --enable-libvmaf libvmaf is version3 and --enable-version3 is not specified. If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem. Thank you, Chris Davis
2018-02-08 20:54 GMT+01:00 Chris Davis <chrisdavis03@gmail.com>:
./configure --enable-libvmaf
libvmaf is version3 and --enable-version3 is not specified.
Are you a native speaker? The error message tries to tell you that instead of "./configure --enable-libvmaf" you should try "./configure --enable-version3 --enable-libvmaf": Do you believe a better wording is easily possible? Carl Eugen
Am 09.02.2018 um 02:23 schrieb Carl Eugen Hoyos:
2018-02-08 20:54 GMT+01:00 Chris Davis <chrisdavis03@gmail.com>:
./configure --enable-libvmaf
libvmaf is version3 and --enable-version3 is not specified.
Are you a native speaker?
The error message tries to tell you that instead of "./configure --enable-libvmaf" you should try "./configure --enable-version3 --enable-libvmaf": Do you believe a better wording is easily possible?
surely, state that it's about GPLv3 "version3" can be all or nothing and is confusing when you build from a ffmpeg-3.x tarball
participants (3)
-
Carl Eugen Hoyos -
Chris Davis -
Reindl Harald