Reclient build errors on Windows

[Ekam Walia]

Hello team!

I am trying to use reclient and bazel-buildfarm to set up a remote execution backend for building windows binaries of chromium but I am running into an error related to the windows SDK as follows

```

[20/58036] CXX obj/base/base_static/static_constants.obj
FAILED: obj/base/base_static/static_constants.obj

..\..\buildtools\reclient\rewrapper -cfg=C:\Users\riturajs.CITRITE\chromium\src\buildtools\reclient_cfgs\linux\chromium-browser-clang\rewrapper_linux.cfg -exec_root=C: -labels=type=compile,compiler=clang-cl,lang=cpp  <args hidden for brevity, full command in logs>

reclient[c55e4b8e-3e51-4b71-90e7-f71d8c5bf70b]: LocalErrorResultStatus: path C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.38.33130\include is not under C:\Users\riturajs.CITRITE\chromium\src\out\Platform-win

```

I raised an issue on github  - https://github.com/bazelbuild/reclient/issues/34 but sharing here in case someone knows the answer.

Thank you!
Ekam

[Michael Savigny]

Hey Ekam,

A couple of questions... 

The first thing to check is from here: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/windows_build_instructions.md#install

Make sure you have followed this step:
"Also, add a DEPOT_TOOLS_WIN_TOOLCHAIN environment variable in the same way, and set it to 0. This tells depot_tools to use your locally installed version of Visual Studio (by default, depot_tools will try to use a google-internal version)."

If you have, can you tell me the directories where you have both depot_tools and chromium/src installed too?

Thanks!

Mike

[Ekam Walia]

Thank you for your response Michael!

I have set the DEPOT_TOOLS_WIN_TOOLCHAIN to 0 acc to the docs. Screenshot below.


The paths for chromium/src and depot tools are
1. depot_tools - C:\Users\riturajs.CITRITE\chromium\depot_tools

2. chromium src (chromium is cloned into a directory called src, "git clone <repo url> src") - C:\Users\riturajs.CITRITE\chromium\src


Thank you!
Ekam

[Ekam Walia]

Hello @Michael!

We are still stuck with this issue. Would you please be able to check my reply above to your questions and share pointers on how we can resolve the issue?

Thank you!
Ekam

[Michael Savigny]

Sorry for the delay, I've responded to the github bug directly.