Actually, one thing that might help, is to enable all possible demuxers/decoders/parsers, — I don't care about licensing at this moment, and only evaluating the media support.Is there an easy way to do this when building ffmpeg?
On Friday, August 12, 2016 at 9:09:03 PM UTC+3, Sergey Podatelev wrote:Hello all,I'm trying to build a ffmpeg.dylib for Chromium with hevc/h265 support enabled.
Here's my build process:export GYP_GENERATORS=ninja; export GYP_DEFINES="branding=Chrome ffmpeg_component=shared_library"; export PYTHONPATH="$PWD/build";./tools/gyp/gyp -I build/common.gypi --depth=. ./third_party/ffmpeg/ffmpeg.gyp
ninja -v -C out/Release ffmpeg
I'm testing some .avi / .mkv files with Chromium player after the build, and get mixed results: sometimes I have no sound, sometimes I get no video.The problem is that not only I'm not sure, where to set the needed flags/update config. files, but also I can't even find a build log that would provide the information about build flags, so I at least know, how the build was configured.Can someone please point me to where I can find the more verbose build logs, and where to set the build config. options that are needed?--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev