Same ninja build error, even after setting up depot_tools and src three times

134 views
Skip to first unread message

Ramneek Sandhu

unread,
Jan 20, 2016, 3:58:23 PM1/20/16
to Chromium-dev


I've followed all the instructions on chromium how-to's to the best of my sanity, and did it like three times fresh out of the box, fearing that I must've screwed up something.

At the end, ninja build stops at "Exact" same point.And since I can't see any descriptive error, I'm unable to figure out what the problem is.

I'd really appreciate any help.

Scott Graham

unread,
Jan 20, 2016, 4:17:42 PM1/20/16
to rumms...@gmail.com, Chromium-dev

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Bruce

unread,
Jan 20, 2016, 8:56:01 PM1/20/16
to Chromium-dev, rumms...@gmail.com
In particular, sysinternals tools such as procmon can be helpful for monitoring what is happening and why it is failing. It could be a permissions issue, insufficient drive space, anti-virus software, etc.

Also, if you copy the output as text instead of as a bitmap then it is searchable and easier for others to see, comment on, expand on, etc.

Ramneek Sandhu

unread,
Jan 20, 2016, 8:59:53 PM1/20/16
to Chromium-dev, rumms...@gmail.com
Thanks for your help! 

Yes I now feel that image is certainly not a good idea. And I won't do that again.

Speaking of the issue itself, I was able to resolve it by turning on @echo in batch file, Scott pointed. And found that it was looking for D3D compiler but it was not there in SDK 10 folder. It was resolved by reinstalling win 10 SDK.
Reply all
Reply to author
Forward
0 new messages