I have successfully built an H.264 MP4 enabled version of Chromium using the instructions at
https://bitbucket.org/chromiumembedded/ ... QuickStart. As I understand it, the source used to build this version is the same as was used for the automated packages at
http://opensource.spotify.com/cefbuilds/index.html. In the CefSharp chat channel, @amaitland said, "CefSharp uses vanilla builds of CEF that are sourced from
http://opensource.spotify.com/cefbuilds/index.html. Track down one of the guides that people have written about compiling with proprietary codecs enabled. [Best] of luck."
The version of Chromium that results from building the GitHub repository should be essentially identical to the version that is generated when the automated builds are used (hosted on opensource.spotify.com). Both builds generate several redistributable files: d3dcompiler_47.dll, libcef.dll, libEGL.dll, libGLESv2.dll, natives_blob.bin, snapshot_blob.bin, and widevinecdmadapter.dll. Theoretically, these should be interchangeable with the versions included in the CefSharp package files, but I'm having no success swapping them out.
I realize this is not a CefSharp support forum but CefSharp is not going to be further developed any time in the near future (if ever) by Alex Maitland. So the challenge is to use the H.264 MP4 enabled browser in conjunction with CefSharp. As I've been digging deeper on this, I
think building the browser from the GitHub repository versus the automated build method on Spotify yields the exact same browser, with (at least) one exception being that the full source build takes the proprietary codec environment variable into account whereas the automated builds do not, because they are already assembled with a canned snapshot of Chromium that cannot ever support proprietary codecs. Am I right or wrong in this understanding?