Python script error building CEF 81 on Windows

[callum]

I've seen other similar posts but I've tried the solutions proposed there and I know things change frequently in Chromium/CEF so what worked for say v79 may no longer work.

Building CEF 81 (branch 4044, #e07275d) with media codecs enabled on Windows. My local build using Windows 10/64 completes as expected and produces a valid build that I can use in my application.

However, I also need to make this work inside our automated build system (TeamCity) which uses Windows Server 2012 r2.

I installed the Windows 10 SDK 10.0.18362.0 on both systems and both also have a fully up to date VS 2017 Professional install.

The error (as per, at least 2 other posts here) is:

Code: Select all

ERROR at //build/toolchain/win/BUILD.gn:49:3: Script returned non-zero exit code.
exec_script("../../vs_toolchain.py",
^----------
Current dir: D:/cef/4044_64/chromium_git/chromium/src/out/Release_GN_x86/
Command: D:/cef/4044_64/depot_tools/bootstrap-3_8_0_chromium_8_bin/python/bin/python.exe D:/cef/4044_64/chromium_git/chromium/src/build/vs_toolchain.py copy_dlls D:/cef/4044_64/chromium_git/chromium/src/out/Release_GN_x86 Release x86
Returned 1 and printed out:
Copying C:\Windows\SysWOW64\msvcp140.dll to D:/cef/4044_64/chromium_git/chromium/src/out/Release_GN_x86\msvcp140.dll...
Copying C:\Windows\SysWOW64\vccorlib140.dll to D:/cef/4044_64/chromium_git/chromium/src/out/Release_GN_x86\vccorlib140.dll...
Copying C:\Windows\SysWOW64\vcruntime140.dll to D:/cef/4044_64/chromium_git/chromium/src/out/Release_GN_x86\vcruntime140.dll...


Those 3 Windows DLLs exist on the TeamCity instance - I think those are the ones that have been copied successfully vs the first one that failed to copy and I can't determine which files are in the list.

I'm going to have to dig a lot deeper but I figured it was worth a quick post here in case someone had already worked around it.

For what it's worth, I was able to get a valid build of CEF 76 some months ago on the same system (older Win 10 SDK as per the wiki docs) so I believe it's possible to do so in this version of Windows.

[magreenblatt]

Did you install all required VS sub-components? See here

[callum]

Did you install all required VS sub-components? See here

Interesting - those look new since I last worked on this 6 months ago - Sorry, I should have checked that page first before posting.

I'll give it a go on the remote box although I have never done that locally either and I was able to get a build.

Still, something to look at - thank you.

[callum]

I confirmed those components are present - reinstalled them again just be sure and confirmed Visual Studio and the SDK are in standard locations.

Is there any way to get a list of files the script is trying to copy so I can see if they are there or not?

[magreenblatt]

You can look at the command that’s being executed and run it manually. Add print statements as needed.

[callum]

You can look at the command that’s being executed and run it manually. Add print statements as needed.

Catching vc_toolchain.py is hard - I have a 30 second window in 50-60 minutes to edit it.. Didn't realize it was Python3 too so prints failed - this is try #3

[callum]

I managed to edit the file and saw this in the output:

Code: Select all

warning: build/vs_toolchain.py has type 100644, expected 100755

then the build proceeded and didn't fail.. still early - takes 12+ hours on my machine - but it's already well past the point it failed at before.

Maybe it couldn't be executed with that 100644 so it didn't at all and the build will inevitably fail later..

[callum]

Script ran overnight on the remote machine outside of TeamCity and completed successfully.

So, either editing vs_toolchain.py stopped it from running normally and that stopped the copy error happening which seems impossible, it means running it under TeamCity is the issue and that makes it much harder to debug.

My prints in the script didn't appear in the command prompt - is that expected and the output goes to a log file somewhere? The prints are still in the file afterwards so they weren't overwritten by an additional checkout.

I will continue to dig..