configure -prefix=/home/khong/ffmpeg_build \ We do not have to enable a library we're not using, so drop it from the configure and carefully monitor each step of compilation.Īctually, I used the following for my configuration: enable-libx264 -enable-nonfree -enable-x11grab -enable-libfaac enable-libmp3lame -enable-libopus -enable-libtheora -enable-libvorbis -enable-libvpx \ bindir="$HOME/bin" -extra-libs="-ldl" -enable-gpl -enable-libass -enable-libfdk-aac \ extra-cflags="-I$HOME/ffmpeg_build/include" -extra-ldflags="-L$HOME/ffmpeg_build/lib" \
configure -prefix="$HOME/ffmpeg_build" \ PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" For example, in the sample given by the guide: If that's not the case, then, I would recommend breaking up the configure line and check if it works. The configuration line should be displayed there, and we can check the libx264 has been enabled. Use -h to get full help or, even better, run 'man ffmpeg' Rm -rf ~/ffmpeg_build ~/ffmpeg_sources ~/bin/. So, whatever the reason that happens, we need to step back and start it over after a few unsuccessful tries.Combining above two may lead all sorts of issues: compilation or load/link error etc.Forgot to remove already installed old packages which may cause dependency or compatiblity issue.configure -prefix="$HOME/ffmpeg_build" -bindir="$HOME/bin" For example, in yasm, we setup the build directory and usr's bin directory: Supposed to be in order due to the dependencies and the env. Failed to follow the steps in the Ubuntu Compilation Guide.However, there could be couple of issues that keep us from successful installation at the first shot. In general, installing ffmpeg supposed to be straight forward.
More general info on ffmpeg is available at. The best site as a reference of compiling ffmpeg on Ubuntu is Ubuntu Compilation Guide.
0 kommentar(er)
