[RESOLVED] Visual Studio update breaks my batch file compiling

[jcfuller]

FYI:
I compile most all my c/c++ code using batch files.
My ide sets environment vars before calling the batch file.
I set INCLUDE to point to my personal include folder and with prior versions this worked fine.
I recently updated my Visual Studio 2017 community and now it cannot find my include folder.
I have another environment var MYINC that also points to my include file.
By using cl.exe /I%MYINC% ...... in the batch files it now works as expected.
It is probably something I should have done in the first place but .....

James

[Arjay]

FYI:
I compile most all my c/c++ code using batch files.
My ide sets environment vars before calling the batch file.
I set INCLUDE to point to my personal include folder and with prior versions this worked fine.
I recently updated my Visual Studio 2017 community and now it cannot find my include folder.
I have another environment var MYINC that also points to my include file.
By using cl.exe /I%MYINC% ...... in the batch files it now works as expected.
It is probably something I should have done in the first place but .....

James

Are you running the batch file from a Visual Studio command prompt?

[jcfuller]

Are you running the batch file from a Visual Studio command prompt?

No I am not. I shell to cmd.exe from my editor. I have been running this way with VS 2013,2015,and 2017 without problems until the last VS 2017 update.

James

[2kaud]

Have you reported it as an issue? See https://developercommunity.visualstu...index.html?all

[jcfuller]

Have you reported it as an issue? See https://developercommunity.visualstu...index.html?all

No I have not because here:
https://docs.microsoft.com/en-us/cpp...ment-variables
it says
INCLUDE, which must point to the \include subdirectory of your Visual C++ installation
So I figured I may have been using it in an undocumented way and for some unknown reason it was working??
Everything is fine now by adding the /I%MYINC% in my batch files. This was more of an FYI post just in case others were having issues. I doubt very many coders use batch files with the latest Visual Studio c/c++ but I thought I'd pass along my findings anyway

James

[Arjay]

Looks like Visual Studio has cleaned up what environment variables it sets during installation. I would guess that it sets less system/user variables during a vs install and relies on folks using the visual studio command prompt when they need a VS cmd env. Try typing c:\set from both command prompts (i.e. regular and Visual Studio) and compare the envirinment variables. The vs cmd prompt is simply a batch file that sets extra env variables. If you want the 'older' build experience simply add missing env variables to the system or user settings.