Error with ninja when tring to build chromium in windows environement

1,015 views
Skip to first unread message

Yann Justdohit

unread,
Oct 24, 2016, 4:11:44 AM10/24/16
to Chromium-dev
Hello everyone,

I try to follow intruction here to compile myself chromium in a win10(x64) environement

are done.

But when i try to `ninja -C out\my_build chrome`
I get this error output :

> ninja: Entering directory `out\my_build'
[1/26855] ACTION //chrome:chrome_dll_manifest__gen_manifest(//build/toolchain/win:x64)
FAILED: gen/chrome/chrome_dll_manifest.manifest
D:/TRAVAIL/depot_tools/python276_bin/python.exe ../../build/toolchain/win/tool_wrapper.py manifest-wrapper environment.x64 mt.exe -nologo -manifest ../../build/win/as_invoker.manifest ../../build/win/common_controls.manifest -out:gen/chrome/chrome_dll_manifest.manifest
The specified path was not found.
[2/26855] RC obj/chrome/chrome_exe_version/chrome_exe_version.res
FAILED: obj/chrome/chrome_exe_version/chrome_exe_version.res

... truncated output ...

I ran `gclient runhooks` & `gn gen out/my_build` whitout any error

I understand that the error message is here "The specified path was not found."

all build launched with ninja command fail with the same error 

"ninja -C out\my_build ui/display:display_unittests", etc...

I tried to search my self the answer but after 2 days no solution are coming

what I'm doing wrong ?

Thx In advance 

Bruce

unread,
Oct 24, 2016, 4:23:41 PM10/24/16
to Chromium-dev
Unfortunately those "path was not found" errors are frustratingly vague - which path wasn't found? Thanks Bill.

Make sure that python exists at that location. Make sure that mt.exe exists - it should be in "C:\Program Files (x86)\Windows Kits\10\bin\x64" and "C:\Program Files (x86)\Windows Kits\10\bin\x86"

And, a good general trouble-shooting tip for this sort of issue is to run sysinternals' procmon and search through its output trying to figure out what file is missing.

My best guess is that the Windows 10 SDK is not correctly installed. Or maybe C++ didn't get installed as part of your VS 2015 installed - it defaults to not installing. Or both.

Yann Justdohit

unread,
Oct 24, 2016, 5:36:30 PM10/24/16
to Chromium-dev
"which path wasn't found? Thanks Bill"
> so true lol

My best guess is that the Windows 10 SDK is not correctly installed. Or maybe C++ didn't get installed as part of your VS 2015 installed - it defaults to not installing. Or both.

>I recently moved the windows 10 SDK to another partition then i used mklink to link C:\Program Files (x86)\Windows Kits\10 to D:\Program Files (x86)\Windows Kits\10 maybe >is for that. 
>I will try to move the SDK to it's origin place & test again.

Thx for your reply ;) I'm so happy to have new clues

Yann Justdohit

unread,
Oct 25, 2016, 8:25:50 AM10/25/16
to Chromium-dev
After removing the hard link the problem remain the same :(

Make sure that python exists at that location.
>Checked -->ok
Make sure that mt.exe exists - it should be in "C:\Program Files (x86)\Windows Kits\10\bin\x64" and "C:\Program Files (x86)\Windows Kits\10\bin\x86"
>Checked -->ok
My best guess is that the Windows 10 SDK is not correctly installed. Or maybe C++ didn't get installed as part of your VS 2015 installed - it defaults to not installing. Or both.
>Checked -->ok

I 'm trying to use  sysinternals' procmon to filter cmd.exe //pyhton.exe // mt.exe // cl.exe // rc.exe and find which path was not found ... but no conclusive results

Any Help will be greatly appreciate

Bruce Dawson

unread,
Oct 25, 2016, 2:08:32 PM10/25/16
to justdoh...@gmail.com, Chromium-dev
You may also need to re-run "gclient sync" and/or "gn gen", in case bad paths got embedded into some files. Maybe look at src\build\win_toolchain.json to see if it looks reasonable?

You could also try explicitly setting up the VS environment:

> "%VS140COMNTOOLS%..\..\VC\vcvarsall.bat" amd64_x86

and then manually running the failing command, with variants, to try to identify the failure point. Unfortunately this is difficult if you don't have a working setup to compare to.

Also, check your args.gn file. It sounds like you don't have any special settings in there, but if you do have any variables set, please share.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to a topic in the Google Groups "Chromium-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-dev/fQjCq1cV1AI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-dev+unsubscribe@chromium.org.

Yann Justdohit

unread,
Oct 26, 2016, 2:35:55 AM10/26/16
to Chromium-dev, justdoh...@gmail.com
I will try all of your instruction and report here when i will finish

Thanks again for your help & interest

Best regards
To unsubscribe from this group and all its topics, send an email to chromium-dev...@chromium.org.

Yann Justdohit

unread,
Oct 27, 2016, 1:24:49 PM10/27/16
to Chromium-dev, justdoh...@gmail.com
Hi,

I tried to reinstall the entire VS2015 + the SDK whitout any success :'(

but one things caught my attention 

>Maybe look at src\build\win_toolchain.json
It's seem I don't have any json file in this directory only bash & python script maybe it's for that ?

I deleted entire /src/out/*

before do gclient sync & gn gen out/default

that's all, i will continue investigation

Bruce

unread,
Oct 29, 2016, 7:43:41 PM10/29/16
to Chromium-dev, justdoh...@gmail.com
Sorry, the build\win_toolchain.json suggestion was a red herring.

The setup of paths (which is what we assume is going wrong here) is in build\vs_toolchain.py, so you may need to try debugging this. Sometimes the best way to get output from these scripts is to raise an exception - normal printing is swallowed in many cases. So, for instance, on my home (non-Google setup) machine I changed the print statement near the end of vs_toolchain.py to raise an exception containing the text instead of printing it:

  raise Exception('''vs_path = "%s"
sdk_path = "%s"
vs_version = "%s"
wdk_dir = "%s"
runtime_dirs = "%s"
''' % (
      NormalizePath(os.environ['GYP_MSVS_OVERRIDE_PATH']),
      NormalizePath(os.environ['WINDOWSSDKDIR']),
      GetVisualStudioVersion(),
      NormalizePath(os.environ.get('WDK_DIR', '')),
      os.path.pathsep.join(runtime_dll_dirs or ['None'])))

Then I ran gn gen (you can run it on an existing or non-existent directory, it doesn't matter). You can see my results below:

> gn gen out\release
Traceback (most recent call last):
  File "C:/src/chromium/src/build/vs_toolchain.py", line 404, in <module>
    sys.exit(main())
  File "C:/src/chromium/src/build/vs_toolchain.py", line 400, in main
    return commands[sys.argv[1]](*sys.argv[2:])
  File "C:/src/chromium/src/build/vs_toolchain.py", line 388, in GetToolchainDir
    os.path.pathsep.join(runtime_dll_dirs or ['None'])))
Exception: vs_path = "C:\Program Files (x86)\Microsoft Visual Studio 14.0"
sdk_path = "C:\Program Files (x86)\Windows Kits\10"
vs_version = "2015"
wdk_dir = ""
runtime_dirs = "C:\Windows\Sysnative;C:\Windows\SysWOW64"

ERROR at //build/config/win/visual_studio_version.gni:27:7: Script returned non-zero exit code.



If your directories are different, or if your VS 14 or Windows Kits\10 directories don't contain all of the expected files, then that's the problem. If not, then, ...?
Reply all
Reply to author
Forward
0 new messages