Master Branch build failed in debug version

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.

Master Branch build failed in debug version

Postby bango » Wed Feb 07, 2018 11:31 am

My machine is Windows 10, Visual Studio 2017 (15.5.1). I'm trying to build the master branch today. My build script:
update.bat:
set CEF_USE_GN=1
set GN_DEFINES=is_win_fastlink=true proprietary_codecs=true ffmpeg_branding=Chrome enable_precompiled_headers=false
set GN_ARGUMENTS=--ide=vs2017 --sln=cef --filters=//cef/*
python automate-git.py --download-dir=c:\Temp\download --depot-tools-dir=c:\Temp\download\depot_tools --no-distrib --no-build


create.bat:
set CEF_USE_GN=1
set GN_DEFINES=is_win_fastlink=true proprietary_codecs=true ffmpeg_branding=Chrome enable_precompiled_headers=false
set GN_ARGUMENTS=--ide=vs2017 --sln=cef --filters=//cef/*
call cef_create_projects.bat


The Release_GN_x86 build finished successfully. But the Debug_GN_x86 build failed with below error:
c:\Temp\download\chromium\src>ninja -C out\Debug_GN_x86 cef
ninja: Entering directory `out\Debug_GN_x86'
[528/3418] ACTION //cef:make_pack_header_resources(//build/toolchain/win:win_clang_x86)
File includes/include/cef_pack_resources.h is already up to date.
[530/3416] ACTION //cef:make_pack_header_strings(//build/toolchain/win:win_clang_x86)
File includes/include/cef_pack_strings.h is already up to date.
[3403/3407] LINK(DLL) libcef.dll libcef.dll.lib libcef.dll.pdb
FAILED: libcef.dll libcef.dll.lib libcef.dll.pdb
c:/Temp/download/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x86 False link.exe /nologo /IMPLIB:./libcef.dll.lib /DLL /OUT:./libcef.dll /PDB:./libcef.dll.pdb @./libcef.dll.rsp
LINK : fatal error LNK1318: Unexpected PDB error; FILE_SYSTEM (3) 'c:\Temp\download\chromium\src\out\Debug_GN_x86\libcef.dll.pdb'
ninja: build stopped: subcommand failed.

The size of libcef.dll.pdb exceeded 4GB. Is there any other way to reduce the size of the PDB file?
bango
Newbie
 
Posts: 3
Joined: Wed Jan 03, 2018 11:35 am

Re: Master Branch build failed in debug version

Postby magreenblatt » Wed Feb 07, 2018 12:18 pm

Don't use is_win_fastlink=true with VS2017.

The use_jumbo_build=true GN value is recommended for debug builds but that might cause issues in combination with proprietary codecs support as discussed in viewtopic.php?f=6&t=15698.

The is_official_build=true GN value will create a debug build that is configured the same as the release build but with debug checks enabled. If you're planning to distribute the resulting build you should use this value in any case.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Master Branch build failed in debug version

Postby bango » Fri Feb 09, 2018 11:16 am

Replace is_win_fastlink=true with is_official_build=true and the build finished without any problem. Thanks a lot for your help!
bango
Newbie
 
Posts: 3
Joined: Wed Jan 03, 2018 11:35 am


Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 83 guests