Building CEF 3809
Windows Server 2016 Datacenter
Version 1607
OS Build 14393.2972
Also installed pywin32 found in viewtopic.php?f=6&t=17258&p=44073&hilit=+windows+build#p44073
Using powershell and on step 7 of the master build quick start `7. Create the "c:\code\chromium_git\chromium\src\cef\create.bat" script with the following contents.`....
- Code: Select all
$env:CEF_USE_GN=1
$env:GN_DEFINES="is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome target_cpu=x86"
$env:GN_ARGUMENTS="--ide=vs2019 --sln=cef --filters=//cef/*"
$env:CEF_VCVARS="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvars32.bat"
cd c:\code\chromium_git\chromium\src\cef
& .\cef_create_projects.bat
Error Output:
- Code: Select all
63 patches total (63 applied, 0 skipped, 0 failed)
Generating CEF project files...
Creating C:\code\chromium_git\chromium\src\out\Release_GN_x86 directory.
Traceback (most recent call last):
File "C:/code/chromium_git/chromium/src/build/toolchain/win/setup_toolchain.py", line 294, in <module>
main()
File "C:/code/chromium_git/chromium/src/build/toolchain/win/setup_toolchain.py", line 286, in main
assert vc_lib_um_path
AssertionError
Traceback (most recent call last):
File "C:/code/chromium_git/chromium/src/build/toolchain/win/setup_toolchain.py", line 294, in <module>
main()
File "C:/code/chromium_git/chromium/src/build/toolchain/win/setup_toolchain.py", line 286, in main
Traceback (most recent call last):
File "tools\gclient_hook.py", line 132, in <module>
RunAction(src_dir, cmd)
File "C:\code\chromium_git\chromium\src\cef\tools\gclient_util.py", line 40, in RunAction
command, cwd=dir, always_show_header=True, print_stdout=True)
File "c:\code\depot_tools\gclient_utils.py", line 614, in CheckCallAndFilter
rv, args, kwargs.get('cwd', None), None, None)
subprocess2.CalledProcessError: Command 'gn gen out\\Release_GN_x86 --ide=vs2019 --sln=cef --filters=//cef/*' returned non-zero exit status 1 in C:\code\chromium_git\chromium\src
assert vc_lib_um_path
AssertionError
ERROR at //build/config/win/BUILD.gn:323:27: Script returned non-zero exit code.
vcvars_toolchain_data = exec_script("../../toolchain/win/setup_toolchain.py",
^----------
Current dir: C:/code/chromium_git/chromium/src/out/Release_GN_x86/
Command: c:/code/depot_tools/bootstrap-3_8_0_chromium_8_bin/python/bin/python.exe C:/code/chromium_git/chromium/src/build/toolchain/win/setup_toolchain.py "C:\Program Files (x86)/Microsoft Visual Studio/2019/Professional" "C:\Program Files (x86)\Windows Kits\10" "C:\Windows\System32;C:\Windows\SysWOW64;Arm64Unused" win x86 none
Returned 1 and printed out:
vc_bin_dir = "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\bin\\HostX64\\x86"
include_flags_I = "\"/I..\\..\\..\\..\\..\\..\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\ATLMFC\\include\" \"/I..\\..\\..\\..\\..\\..\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\include\""
include_flags_imsvc = "\"-imsvc..\\..\\..\\..\\..\\..\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\ATLMFC\\include\" \"-imsvc..\\..\\..\\..\\..\\..\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\include\""
vc_lib_path = "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\lib\\x86"
vc_lib_atlmfc_path = "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.24.28314\\ATLMFC\\lib\\x86"
See //build/config/BUILDCONFIG.gn:446:5: which caused the file to be included.
"//build/config/win:nominmax",
^----------------------------
LastExitCode: 1
If I simply login to this build box, open powershell, and execute the script the build works fine. I cannot figure out why jenkins would yield different results... I've even tried running the script multiple times (on Jenkins), but it fails on the same step 7 of the masterbuildquickstart guide. While we can produce the binaries we need with manual intervention, we need to automate this. Any suggestions are much appreciated.