Ninja fails on buliding.

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.

Ninja fails on buliding.

Postby cazorla » Fri Dec 15, 2017 4:25 am

I am using vs2015 u3. This is the log generated. What could be the reason behind this.
--> C:\cefbranch\chromium\src\out\Debug_GN_x86\args.gn contents:
enable_basic_printing=true
enable_nacl=false
enable_print_preview=false
enable_widevine=true
is_component_build=false
is_debug=true
target_cpu="x86"
-------- Running "ninja -C out\Debug_GN_x86 cefclient" in "C:\cefbranch\chromium\src"...
ninja: Entering directory `out\Debug_GN_x86'
[7/30934] ACTION //base/trace_event/etw_manifest:chrome_events_win(//build/toolchain/win:x86)
FAILED: gen/base/trace_event/etw_manifest/chrome_events_win.h gen/base/trace_event/etw_manifest/chrome_events_win.rc
C:/cefbranch/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/win/message_compiler.py environment.x86 -h gen/base/trace_event/etw_manifest -r gen/base/trace_event/etw_manifest -u -um ../../base/trace_event/etw_manifest/chrome_events_win.man
'mc.exe' is not recognized as an internal or external command,
operable program or batch file.

[11/30934] CC obj/base/third_party/dynamic_annotations/dynamic_annotations/dynamic_annotations.obj
FAILED: obj/base/third_party/dynamic_annotations/dynamic_annotations/dynamic_annotations.obj
ninja -t msvc -e environment.x86 -- "c:\program files (x86)\microsoft visual studio 14.0\vc\bin\amd64_x86/cl.exe" /nologo /showIncludes @obj/base/third_party/dynamic_annotations/dynamic_annotations/dynamic_annotations.obj.rsp /c ../../base/third_party/dynamic_annotations/dynamic_annotations.c /Foobj/base/third_party/dynamic_annotations/dynamic_annotations/dynamic_annotations.obj /Fd"obj/base/third_party/dynamic_annotations/dynamic_annotations_c.pdb"
../../base/third_party/dynamic_annotations/dynamic_annotations.c(28): fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
[12/30934] CXX obj/breakpad/breakpad_handler/exception_handler.obj
FAILED: obj/breakpad/breakpad_handler/exception_handler.obj
ninja -t msvc -e environment.x86 -- "c:\program files (x86)\microsoft visual studio 14.0\vc\bin\amd64_x86/cl.exe" /nologo /showIncludes @obj/breakpad/breakpad_handler/exception_handler.obj.rsp /c ../../breakpad/src/client/windows/handler/exception_handler.cc /Foobj/breakpad/breakpad_handler/exception_handler.obj /Fd"obj/breakpad/breakpad_handler_cc.pdb"
../../breakpad/src/client/windows/handler/exception_handler.cc(30): fatal error C1083: Cannot open include file: 'objbase.h': No such file or directory
[16/30934] CXX obj/breakpad/breakpad_handler/crash_generation_server.obj
FAILED: obj/breakpad/breakpad_handler/crash_generation_server.obj
ninja -t msvc -e environment.x86 -- "c:\program files (x86)\microsoft visual studio 14.0\vc\bin\amd64_x86/cl.exe" /nologo /showIncludes @obj/breakpad/breakpad_handler/crash_generation_server.obj.rsp /c ../../breakpad/src/client/windows/crash_generation/crash_generation_server.cc /Foobj/breakpad/breakpad_handler/crash_generation_server.obj /Fd"obj/breakpad/breakpad_handler_cc.pdb"
C:\cefbranch\chromium\src\breakpad\src\client/windows/common/ipc_protocol.h(33): fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "test.py", line 1085, in <module>
if options.buildlogfile else None)
File "test.py", line 55, in run
args, cwd=working_dir, env=env, shell=(sys.platform == 'win32'))
File "C:\Python27\lib\subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ninja', '-C', 'out\\Debug_GN_x86', 'cefclient']' returned non-zero exit status 1
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Re: Ninja fails on buliding.

Postby magreenblatt » Fri Dec 15, 2017 12:11 pm

What CEF branch are you building? Did you install the build requirements specified at https://bitbucket.org/chromiumembedded/ ... uilding.md ?
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm

Re: Ninja fails on buliding.

Postby cazorla » Sat Dec 16, 2017 4:38 am

Branch 3202. I have visual studio 2015 update 3 and windows kit 10. I have set the required environment variables as well.
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Re: Ninja fails on buliding.

Postby magreenblatt » Sat Dec 16, 2017 9:59 am

Did you install Visual Studio and SDK to the default locations?
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm

Re: Ninja fails on buliding.

Postby cazorla » Mon Dec 18, 2017 12:51 am

Yes. I have installed them at default locations. Do I need to download/install ninja explicitly? because ninja.exe is available as a part of depot tools. What could be the reason for this build error?
I have set these environment variables GYP_GENERATORS=ninja,msvs-ninja and GYP_MSVS_VERSION=2015. Windows SDK version is 10.1.16299.91 and I am using vs2015 enterprise edition.
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Re: Ninja fails on buliding.

Postby magreenblatt » Mon Dec 18, 2017 12:22 pm

Looks like something wrong with your local setup because it's not finding the Windows header files. What are the contents of your out\Debug_GN_x86\environment.x86 file? Are you building using cmd.exe?
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm

Re: Ninja fails on buliding.

Postby cazorla » Tue Dec 19, 2017 6:43 am

I uninstalled the windows kit 10.1 and reinstalled the windows kit mectioned in the wiki page. Now cef build continued and got an error here
-------- Running "ninja -C out\Debug_GN_x64 cefclient" in "C:\cefbranch\chromium\src"...
ninja: Entering directory `out\Debug_GN_x64'
[16785/30928] ACTION //cef:make_pack_header_strings(//build/toolchain/win:x64)
File includes/include/cef_pack_strings.h updated.
[16787/30928] ACTION //cef:make_pack_header_resources(//build/toolchain/win:x64)
File includes/include/cef_pack_resources.h updated.
[30927/30928] LINK(DLL) libcef.dll libcef.dll.lib libcef.dll.pdb
FAILED: libcef.dll libcef.dll.lib libcef.dll.pdb
C:/cefbranch/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x64 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:\cefbranch\chromium\src\out\Debug_GN_x64\libcef.dll.pdb'
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "test.py", line 1085, in <module>
if options.buildlogfile else None)
File "test.py", line 55, in run
args, cwd=working_dir, env=env, shell=(sys.platform == 'win32'))
File "C:\Python27\lib\subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ninja', '-C', 'out\\Debug_GN_x64', 'cefclient']' returned non-zero exit status 1

It took almost 5.5 hours to come to this stage.
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Re: Ninja fails on buliding.

Postby cazorla » Tue Dec 19, 2017 6:49 am

Is there any way to continue the build from this point.. rather than building it from the beginning.
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Re: Ninja fails on buliding.

Postby magreenblatt » Tue Dec 19, 2017 10:29 am

You will probably need to set GN_DEFINES=is_win_fastlink=true and then re-run automate-git.py for the build to succeed. You can also run the following manually:

Code: Select all
cd c:\path\to\chromium\src\cef
set GN_DEFINES=is_win_fastlink=true
set GN_ARGUMENTS=--ide=vs2015 --sln=cef --filters=//cef/*
cef_create_projects.bat

cd ..
ninja -C out\Debug_GN_x64 cef
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm

Re: Ninja fails on buliding.

Postby cazorla » Wed Dec 20, 2017 12:41 am

I tried the manual method and got this
C:\cefbranch\cef>set GN_DEFINES=is_win_fastlink=true

C:\cefbranch\cef>set GN_ARGUMENTS=--ide=vs2015 --sln=cef --filters=//cef/*

C:\cefbranch\cef>cef_create_projects.bat

Generating CEF version header file...
________ running 'C:\cefbranch\depot_tools\win_tools-2_7_6_bin\python\bin\python.exe tools/make_version_header.py --header include/cef_version.h --cef_version VERSION --chrome_version ../chrome/VERSION --cpp_header_dir include' in 'C:\cefbranch\cef'
Traceback (most recent call last):
File "tools/make_version_header.py", line 188, in <module>
options.cef_version, options.cpp_header_dir)
File "tools/make_version_header.py", line 64, in write_version_header
' does not exist.')
Exception: Chrome version file ../chrome/VERSION does not exist.
Traceback (most recent call last):
File "tools\gclient_hook.py", line 34, in <module>
RunAction(cef_dir, cmd)
File "C:\cefbranch\cef\tools\gclient_util.py", line 39, in RunAction
gclient_utils.CheckCallAndFilterAndHeader(command, cwd=dir, always=True)
File "C:\cefbranch\depot_tools\gclient_utils.py", line 314, in CheckCallAndFilterAndHeader
return CheckCallAndFilter(args, **kwargs)
File "C:\cefbranch\depot_tools\gclient_utils.py", line 560, in CheckCallAndFilter
rv, args, kwargs.get('cwd', None), None, None)
subprocess2.CalledProcessError: Command 'C:\\cefbranch\\depot_tools\\win_tools-2_7_6_bin\\python\\bin\\python.exe tools/make_version_header.py --header include/cef_version.h --cef_version VERSION --chrome_version ../chrome/VERSION --cpp_header_dir include' returned non-zero exit status 1 in C:\cefbranch\cef
.
cazorla
Newbie
 
Posts: 9
Joined: Thu Nov 30, 2017 4:17 am

Next

Return to Support Forum

Who is online

Users browsing this forum: No registered users and 41 guests