On Mon, 10 May 2021 05:54:51 GMT, John Neffenger wrote:
>> The Windows build calls a series of batch files to get the Visual Studio
>> paths and environment variables. The batch files are a black box: any
>> messages they print are discarded. If anything goes wrong, the only signs
>> are a
> The Windows build calls a series of batch files to get the Visual Studio
> paths and environment variables. The batch files are a black box: any
> messages they print are discarded. If anything goes wrong, the only signs are
> a vague Gradle exception and a corrupted properties file.
>
>
On Fri, 7 May 2021 13:42:49 GMT, Kevin Rushforth wrote:
> It would be more convenient to ask the developer set `VSCMD_DEBUG` via an env
> variable, rather than asking them to edit `win.gradle`.
Thanks, Kevin. That is the most direct approach. I didn't document it that way
for the following
On Thu, 6 May 2021 20:39:11 GMT, John Neffenger wrote:
> The Windows build calls a series of batch files to get the Visual Studio
> paths and environment variables. The batch files are a black box: any
> messages they print are discarded. If anything goes wrong, the only signs are
> a vague
On 5/6/21 1:46 PM, John Neffenger wrote:
$ reg query "HKLM\SOFTWARE\Microsoft\VisualStudio\VSPerf" \
The last part of my comment was truncated by Skara when it tripped over
the '/v' Windows command-line option. It's repeated below for the
mailing list ...
We could instead set the default
On Thu, 6 May 2021 20:39:11 GMT, John Neffenger wrote:
> The Windows build calls a series of batch files to get the Visual Studio
> paths and environment variables. The batch files are a black box: any
> messages they print are discarded. If anything goes wrong, the only signs are
> a vague
The Windows build calls a series of batch files to get the Visual Studio paths
and environment variables. The batch files are a black box: any messages they
print are discarded. If anything goes wrong, the only signs are a vague Gradle
exception and a corrupted properties file.
This has been