Problem building 4430 branch in Windows 10

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.

Problem building 4430 branch in Windows 10

Postby rjxray » Thu Aug 05, 2021 8:39 am

I'm having a problem building 4430 branch in Windows 10 .
I'm building in a command window with
D:\CefBuild4430>python automate\automate-git.py --download-dir=d:\Cefbuild4430 --depot-tools-dir=d:\Cefbuild4430\depot_tools --branch=4430 --x64-build

After generating CEF project files it gets to ACTION [5591/49517] and I'm seeing

Code: Select all
--> d:\Cefbuild4430\chromium\src\out\Debug_GN_x64\args.gn contents:
chrome_pgo_phase=0
clang_use_chrome_plugins=false
dcheck_always_on=true
enable_background_mode=false
enable_basic_printing=true
enable_nacl=false
enable_print_preview=true
enable_resource_allowlist_generation=false
enable_widevine=true
ffmpeg_branding="Chrome"
forbid_non_component_debug_builds=false
is_component_build=false
is_debug=false
is_official_build=true
optimize_webui=true
proprietary_codecs=true
target_cpu="x64"
-------- Running "ninja -C out\Debug_GN_x64 cefclient" in "d:\Cefbuild4430\chromium\src"...
ninja: Entering directory `out\Debug_GN_x64'
[5591/49517] ACTION //third_party/devtools-frontend/src/te...ductor:implementation(//build/toolchain/win:win_clang_x64)
FAILED: gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json.tsbuildinfo gen/third_party/devtools-frontend/src/test/conductor/custom-query-handlers.js gen/third_party/devtools-frontend/src/test/conductor/custom-query-handlers.js.map gen/third_party/devtools-frontend/src/test/conductor/custom-query-handlers.d.ts gen/third_party/devtools-frontend/src/test/conductor/hooks.js gen/third_party/devtools-frontend/src/test/conductor/hooks.js.map gen/third_party/devtools-frontend/src/test/conductor/hooks.d.ts gen/third_party/devtools-frontend/src/test/conductor/mocha_hooks.js gen/third_party/devtools-frontend/src/test/conductor/mocha_hooks.js.map gen/third_party/devtools-frontend/src/test/conductor/mocha_hooks.d.ts gen/third_party/devtools-frontend/src/test/conductor/puppeteer-state.js gen/third_party/devtools-frontend/src/test/conductor/puppeteer-state.js.map gen/third_party/devtools-frontend/src/test/conductor/puppeteer-state.d.ts gen/third_party/devtools-frontend/src/test/conductor/test_server.js gen/third_party/devtools-frontend/src/test/conductor/test_server.js.map gen/third_party/devtools-frontend/src/test/conductor/test_server.d.ts
d:/CefBuild4430/depot_tools/bootstrap-2@3_8_10_chromium_20_bin/python/bin/python.exe ../../third_party/devtools-frontend/src/third_party/typescript/ts_library.py --tsconfig_output_location gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json --front_end_directory ../../third_party/devtools-frontend/src/test/conductor --test-only --module=commonjs --sources ../../third_party/devtools-frontend/src/test/conductor/custom-query-handlers.ts ../../third_party/devtools-frontend/src/test/conductor/hooks.ts ../../third_party/devtools-frontend/src/test/conductor/mocha_hooks.ts ../../third_party/devtools-frontend/src/test/conductor/puppeteer-state.ts ../../third_party/devtools-frontend/src/test/conductor/test_server.ts

TypeScript compilation failed. Used tsconfig gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json

error TS1149: File name 'D:/CefBuild4430/chromium/src/third_party/devtools-frontend/src/node_modules/@types/filesystem/index.d.ts' differs from already included file name 'd:/Cefbuild4430/chromium/src/third_party/devtools-frontend/src/node_modules/@types/filesystem/index.d.ts' only in casing.
  The file is in the program because:
    Part of 'files' list in tsconfig.json
    Entry point for implicit type library 'filesystem' with packageId '@types/filesystem/index.d.ts@0.0.29'


[5604/49517] ACTION //third_party/devtools-frontend/src/fr...mon:common-typescript(//build/toolchain/win:win_clang_x64)
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "automate\automate-git.py", line 1483, in <module>
    run(command + build_path + target, chromium_src_dir, depot_tools_dir,
  File "automate\automate-git.py", line 69, in run
    return subprocess.check_call(
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0\lib\subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ninja', '-C', 'out\\Debug_GN_x64', 'cefclient']' returned non-zero exit status 1.


I've built many previous versions in the past in this manner (lastly 4324) and remembered the first thing to check in case of errors is the Windows build requirements for the version which in this case are Win 7+ deployment, Win 10+ build system w/ VS2019 16.8.4+, Win 10.0.19041 SDK, Ninja

I have the required Windows SDK but my VS2019 version is 16.4.3 so I went to update at https://visualstudio.microsoft.com/downloads/ but saw the latest available version is 16.4.7.

So I'm a bit stuck for ideas now so I would be very grateful if anyone has any ideas about what the actual problem might be.

In the meantime I'll update VS 2019 to 16.4.7
rjxray
Expert
 
Posts: 115
Joined: Wed Jun 07, 2017 4:31 am

Re: Problem building 4430 branch in Windows 10

Postby rjxray » Thu Aug 05, 2021 8:43 am

Actually I just realised that the list of versions was previous versions and that it will install version 16.10.
So I'll see if that works
rjxray
Expert
 
Posts: 115
Joined: Wed Jun 07, 2017 4:31 am

Re: Problem building 4430 branch in Windows 10

Postby rjxray » Thu Aug 05, 2021 10:43 am

Well I've updated to VS2019 16.10 and I still have the issue.

Any ideas anyone?
rjxray
Expert
 
Posts: 115
Joined: Wed Jun 07, 2017 4:31 am

Re: Problem building 4430 branch in Windows 10

Postby magreenblatt » Thu Aug 05, 2021 12:07 pm

Code: Select all
d:/CefBuild4430/depot_tools/bootstrap-2@3_8_10_chromium_20_bin/python/bin/python.exe ../../third_party/devtools-frontend/src/third_party/typescript/ts_library.py --tsconfig_output_location gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json --front_end_directory ../../third_party/devtools-frontend/src/test/conductor --test-only --module=commonjs --sources ../../third_party/devtools-frontend/src/test/conductor/custom-query-handlers.ts ../../third_party/devtools-frontend/src/test/conductor/hooks.ts ../../third_party/devtools-frontend/src/test/conductor/mocha_hooks.ts ../../third_party/devtools-frontend/src/test/conductor/puppeteer-state.ts ../../third_party/devtools-frontend/src/test/conductor/test_server.ts

TypeScript compilation failed. Used tsconfig gen/third_party/devtools-frontend/src/test/conductor/implementation-tsconfig.json

error TS1149: File name 'D:/CefBuild4430/chromium/src/third_party/devtools-frontend/src/node_modules/@types/filesystem/index.d.ts' differs from already included file name 'd:/Cefbuild4430/chromium/src/third_party/devtools-frontend/src/node_modules/@types/filesystem/index.d.ts' only in casing.
  The file is in the program because:
    Part of 'files' list in tsconfig.json
    Entry point for implicit type library 'filesystem' with packageId '@types/filesystem/index.d.ts@0.0.29'

Looks like your directory is named "D:\CefBuild4430" but you're passing "d:\Cefbuild4430" in the command-line arguments. Try using "D:\CefBuild4430" everywhere.
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Problem building 4430 branch in Windows 10

Postby rjxray » Fri Aug 06, 2021 8:10 am

Thanks Marshall,

I tried changing the command line as suggested to
Code: Select all
python automate\automate-git.py --download-dir=D:\CefBuild4430 --depot-tools-dir=D:\CefBuild4430\depot_tools --branch=4430 --x64-build

But I still got the error, so I deleted the whole Cefbuild4430 folder, created a new one called CEFBUILD4430 and started again from scratch with the appropriate automate-git arguments

Its now got past the point where it failed so looks like it will be OK.
rjxray
Expert
 
Posts: 115
Joined: Wed Jun 07, 2017 4:31 am


Return to Support Forum

Who is online

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