My question is similar to this one that was asked nearly 3 years ago.
I would like to compile Chromium with support for MP3, AAC, etc. on Mac OS X (I'm using 10.11.6 El Capitan). So far I managed to compile it with standard settings according to the instructions on chromium.org. After running the HTML5Test I realized that by default it doesn't compile with support for proprietary codecs like MP3.
After some googling I found this page on the Chromium.org website which mentioned some compiler flags:
ffmpeg_branding Overrides which version of FFmpeg to use Default: $(branding) Values: Chrome - includes additional proprietary codecs (MP3, etc..) for use with Google Chrome Chromium - builds default set of codecs proprietary_codecs Alters the list of codecs Chromium claims to support, which affects <source> and canPlayType() behaviour Default: 0(gyp)/false(gn) Values: 0/false - <source> and canPlayType() assume the default set of codecs 1/true - <source> and canPlayType() assume they support additional proprietary codecs
I added both to my args.gn using
gn args out/gn but it resulted in a linker error when building with dozens of lines like this:
duplicate symbol in: obj/components/policy/proto/libproto_internal.a(device_management_backend.pb.o)
I removed the first flag and run
ninja again, which resulted in the same linker error after only a few seconds. I switched things around and now left out the second flag I added and it started compiling all over again.
After compiling successfully for another hour, it results in the same version like previously giving me the same HTML5Test result of not supporting MP3/AAC.
My question is now, how can I compile Chromium with support for these codecs?