V33 breaks vcvars64.bat

[vefatica]

I had a pretty hard time building ONIG.DLL. TCCv33 doesn't handle vcvars64.bat very well. Below, I put some newlines in LIBPATH's value to make it easier to read here. Note the empty string in TCCv33's [vcvarsall.bat] Environment initialized for: ''

CMD:

C:\Users\vefatica> "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat"
setting ****X64****
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.11.3
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'

C:\Users\vefatica> echo %libpath%
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\ATLMFC\lib\x64;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x64;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x86\store\references;
C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.22000.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.22000.0;
C:\Windows\Microsoft.NET\Framework64\v4.0.30319

TCCv33: (doesn't set anything for x64)

v:\> "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat"
setting ****X64****
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.11.3
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: ''

v:\> echo %libpath
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\ATLMFC\lib\x86;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x86;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x86\store\references;
C:\Windows\Microsoft.NET\Framework\v4.0.30319

TCCv32: (matches CMD, I think)

v:\> "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat"
setting ****X64****
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.11.3
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'

v:\> echo %libpath
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\ATLMFC\lib\x64;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x64;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\lib\x86\store\references;
C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.22000.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.22000.0;
C:\Windows\Microsoft.NET\Framework64\v4.0.30319

 

[Joe Caverly]

Not the exact same version of VS2022 that Vince has,
but still does not work here.

E:\Utils>ver 

TCC  32.10.21 x64   Windows 10 [Version 10.0.19045.4894]

E:\Utils>vc64 
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.10.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'

E:\Utils>ver 

TCC  33.00.7 x64   Windows 10 

E:\Utils>vc64 
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.10.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: ''

E:\Utils>alias vc64 
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat"

Joe

 

[rconn]

Microsoft VS2022 bug - not in the compiler per se, but in the code analysis tool. The code analysis generated an error for two lines of code in the variable expansion function and insisted they be changed/moved. But doing that resulted in breaking the (klunky CMD) ~... variable parser. I've fixed / restored this for build 9.

 

[Joe Caverly]

Working now.

Thanks Rex.

E:\Utils>vc64 
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.10.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'

E:\Utils>ver 

TCC  33.00.9 x64   Windows 10 [Version 10.0.19045.4894]

Joe