Environment variable "SYSTEMROOT" required to be set to valid path

[rpaquay]

On a Windows machine, after moving my "depot_tools" directory to another drive, running "gclient runhooks" always generates the following error:

Environment variable "SYSTEMROOT" required to be set to valid path

After some digging around, it seems the issue is related to the content of the "win_toolchain\data.json" file. For example:

{

  "runtime_dirs": ["d:\\src\\chromium\\depot_tools_win8\\win_toolchain\\vs2013_files\\sys64", "d:\\src\\chromium\\depot_tools_win8\\win_toolchain\\vs2013_files\\sys32"],

   "path": "d:\\src\\chromium\\depot_tools_win8\\win_toolchain\\vs2013_files",

   "version": "2013",

   "wdk": "d:\\src\\chromium\\depot_tools_win8\\win_toolchain\\vs2013_files\\wdk",

   "win8sdk": "d:\\src\\chromium\\depot_tools_win8\\win_toolchain\\vs2013_files\\win8sdk"

}

The directory in "bold" is the former location of "depot_tools" (and that directory does not exist anymore). It seems this file is not updated automatically by "gclient runhooks" after the "depot_tools" directory is moved to another location.

Is this expected behavior? Is there some "magic incantation" command I can run to update this file to reflect the new directory location (and what is it?)

[Scott Graham]

I'm sorry the error is so obscure, a patch to make the error condition more clear would be great.

rmdir /s/q d:\new_depot_tools_location\win_toolchain\vs2013_files && gclient runhooks

is probably the simplest fix. We could also look at fixing the "move" case, but I'm not sure if it's worth worrying about unless there's some reason to do that frequently.

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