Yes, the sample app works.
Here is the process I use, which was pieced together from multiple forum posts and other sources. If there's a better way I would love to learn it!
My goal is to create a binary distribution identical to the official download, with two changes:
- h264 support
- A libcef_dll_wrapper that uses /MD for the Runtime Library (or /MDd for debug).
I mostly follow the instructions found on the MasterBuildQuickStart page. I add "is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome" to the update and the create scripts:
- Code: Select all
set GN_DEFINES=is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome
set GN_ARGUMENTS=--ide=vs2017 --sln=cef --filters=//cef/*
set GYP_MSVS_VERSION=2017
set CEF_ARCHIVE_FORMAT=tar.bz2
python ..\automate\automate-git.py --download-dir=c:\code\chromium_git4103 --depot-tools-dir=c:\code\depot_tools --branch=4103 --minimal-distrib --client-distrib --force-clean --x64-build
- Code: Select all
set GN_DEFINES=is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome
set GN_ARGUMENTS=--ide=vs2017 --sln=cef --filters=//cef/*
call cef_create_projects.bat
Then I call make_distrib.bat to make a distribution:
- Code: Select all
make_distrib.bat --ninja-build --x64-build
From that distribution (in this case cef_binary_83.4.5+ga4a78d1+chromium-83.0.4103.106_windows64) i use cmake to generate the 64 bit VS project files. Then I open the project and change the runtime library for the libcef_dll_wrapper project, and recompile debug and release.
Then I copy the include files along with all the necessary dlls and resource files from the distribution to where my project expects them to be.
I did find the libcef pdb file, so I was able to load that and get a much nicer stack trace. I've attached the full stack trace, but it appears as though AcceptLanguageBuilder::AddLanguageCode is being called with "*;q=0.5" and the function doesn't like having the semi-colon in there.
- StackTrace.PNG (531.43 KiB) Viewed 4000 times