VideoHelp Forum




+ Reply to Thread
Results 1 to 4 of 4
  1. I cant enable x265 in FFmpeg

    Code:
    siraj@RouterX:~/ffmpeg_sources/ffmpeg$ PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure \--prefix="$HOME/ffmpeg_build" \
    >   --extra-cflags="-I$HOME/ffmpeg_build/include" \
    >   --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
    >   --bindir="$HOME/bin" \
    >   --pkg-config-flags="--static" \
    >   --enable-gpl \
    >   --enable-libass \
    >   --enable-libfdk-aac \
    >   --enable-libfreetype \
    >   --enable-libmp3lame \
    >   --enable-libopus \
    >   --enable-openssl \
    >   --enable-libvorbis \
    >   --enable-libvpx \
    >   --enable-libx264 \
    >   --enable-libx265 \
    >   --enable-nonfree
    ERROR: x265 not found using pkg-config
    
    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.
    I followed these instructions, but the problem still remains :

    https://bitbucket.org/multicoreware/x265/issues/125/x265-not-found-using-pkg-config
    Quote Quote  
  2. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    This is a known issue for the media-autobuild_suite: The x265 team keeps using a "bool" data type, which is discouraged in many other projects because it is handled in different ways in different C/C++ compilers (e.g. MS Visual C++ 2012 / Visual Studio 11 handles it differently, doesn't like stdbool.h). It will be fixed soon™. In the meantime, you can go back to a x265 revision before commit c258d21.
    Quote Quote  
  3. Originally Posted by LigH.de View Post
    This is a known issue for the media-autobuild_suite: The x265 team keeps using a "bool" data type, which is discouraged in many other projects because it is handled in different ways in different C/C++ compilers (e.g. MS Visual C++ 2012 / Visual Studio 11 handles it differently, doesn't like stdbool.h). It will be fixed soon™. In the meantime, you can go back to a x265 revision before commit c258d21.
    thank you, I fixed the problem by Adding :

    #include <stdbool.h>

    to source/x265.h then ./configure FFmpeg again
    Quote Quote  
  4. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    A more elaborate fix is being proposed in the mailing list and will probably be available until tomorrow.

    They will avoid a "bool" field in a structure and use an "int" instead.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!