autoninja -C out\Default chrome throws an error

603 views
Skip to first unread message

Yoav Linder

unread,
Apr 1, 2024, 3:08:38 PM4/1/24
to Chromium-dev
hi, i am trying to build my chrome with autoninja -C out\Default chrome, but it throws this error:
C:\projects\chromium\src>autoninja -C out\Default chrome
depot_tools/ninja.py: Could not find Ninja in the third_party of the current project, nor in your PATH.
Please take one of the following actions to install Ninja:
- If your project has DEPS, add a CIPD Ninja dependency to DEPS.
- Otherwise, add Ninja to your PATH *after* depot_tools.

the PATH has the depot tools,it happened since i ran this command:
gclient sync --reset --revision src@refs/tags/96.0.4664.110 --no-history

anyone knows what the problem can be?

K. Moon

unread,
Apr 2, 2024, 4:04:08 AM4/2/24
to linde...@gmail.com, Chromium-dev
Newer versions of depot_tools expect Ninja to be provided by the source tree, via gclient. The version of Chromium you've synced does not do this.

In general, it's impossible (and unsupported) to build older versions of Chromium with newer versions of depot_tools.

--
--
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 the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/9040b21c-2b78-4564-ad96-798e446718aan%40chromium.org.

Bruce Dawson

unread,
Apr 3, 2024, 4:08:19 PM4/3/24
to Chromium-dev, K. Moon, Chromium-dev, linde...@gmail.com
You could sync depot_tools to an older date, and then prevent it from updating with "set DEPOT_TOOLS_UPDATE=0". Or you could do what the error message suggests and add ninja to your path after depot_tools. Since ninja.exe ships with Visual Studio I sometimes do this by running this command to add the VS tools to the current path:

"c:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvarsall.bat" amd64

Reply all
Reply to author
Forward
0 new messages