Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

CMD, TCC, VisualStudio 2017, VcVars* differences

May
14
0
I am setting up a new laptop at a new job and encountered a discrepancy between CMD and TCC.

The attached 7z file contains dumps of the environment variables before and after running vcvars32.bat. The environment variables that have different values are:
FrameworkDir,
INCLUDE,
LIB,
LIBPATH,
PATH,
UCRTVersion,
WindowsLibPath,
WindowsSDKLibVersion,
WindowsSdkVerBinPath,
WindowsSdkVerBinPath

My system information is: Microsoft Windows 10 Pro (Version 10.0.16299 Build 16299), TCC 22.00.42 x64, Microsoft Visual Studio Community 2017 (Version 15.7.1; VisualStudio.15.Release/15.7.1+27703.2000).


Any suggestions on how to handle this or what to look at?
 

Attachments

  • Difs.7z
    2.1 KB · Views: 291
I tried this with an almost identical setup (except I'm using VS 15.7.2 and Windows 10 Build 17677), and I cannot reproduce your results. The only differences I get are a result of the TCC-only environment variables (like CMDLINE).

If I had to guess, I'd say you probably turned off some CMD compatibility settings in your TCMD.INI. Try it without loading your TCMD.INI and see if you get the same results.
 

Similar threads

Replies
0
Views
1K
Back
Top