Can't use the result of Automated build

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Can't use the result of Automated build

Postby Serhii » Mon Mar 22, 2021 7:19 am

I do the steps described in the instructions https://bitbucket.org/chromiumembedded/ ... dows-setup.
I replaced the bat file in step 6 with
set GN_DEFINES=is_component_build=false is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome
# Use vs2017 or vs2019 as appropriate.
set GN_ARGUMENTS=--ide=vs2019 --sln=cef --filters=//cef/*
python ..\automate\automate-git.py --download-dir=c:\code\chromium_git --depot-tools-dir=c:\code\depot_tools --no-distrib --no-build
and step 7 with
set GN_DEFINES=is_component_build=true proprietary_codecs=true ffmpeg_branding=Chrome
# Use vs2017 or vs2019 as appropriate.
set GN_ARGUMENTS=--ide=vs2019 --sln=cef --filters=//cef/*
call cef_create_projects.bat.
Actually sample exe works fine but I don't receive the same dlls like here https://cef-builds.spotifycdn.com/index.html#windows64, for example cef.pak is absent and chrome_elf.lib is absent but chrome_elf.dll.lib is present. Do I do something wrong to get CEF with proprietary_codecs available in my C++ project? I have already CEF as it is distributed but need to enable h264 codec.
Serhii
Newbie
 
Posts: 2
Joined: Thu Jan 14, 2021 6:10 am

Re: Can't use the result of Automated build

Postby magreenblatt » Mon Mar 22, 2021 8:30 am

If you're building master the pak file names have recently changed. You should compare your build to the M89 (current beta) builds, and check the included README.txt file.
magreenblatt
Site Admin
 
Posts: 12402
Joined: Fri May 29, 2009 6:57 pm


Return to Support Forum

Who is online

Users browsing this forum: No registered users and 47 guests