Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 24 Apr 2024 01:49:05 +0000
Incorrect parsing of Env Variable VS140COMNTOOLS
View Count: 1905
| [2021-04-03 18:12:00] |
| autobahn - Posts: 25 |
|
When compiling a custom study locally, the environment variable VS140COMNTOOLS is used to determine the location of vcvarsall.bat. Visual Studio Build Tools 2017 uses the following location for vcvarsall.bat: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat
However, specifying this path in the environment variable always results in VisualCCompile.bat incorrectly trying to use the following location: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\VC\vcvarsall.bat
This is because Sierra Chart (2245 64-bit 36772) always adds \VC to the end of the path. This was correct operation for VS2015, but incorrect for VS2017 and VS2019. A workaround is to create a dummy vcvarsall.bat file that SierraChart can locate, and have that dummy file call the proper vcvarsall.bat file. |
| [2021-04-03 18:13:29] |
| autobahn - Posts: 25 |
|
Note for anybody else experiencing this issue: When you change the environment variable, it is necessary to completely exit and restart Sierra Chart for the new variable to take effect.
|
| [2021-04-05 15:39:59] |
| |
|
This is because Sierra Chart (2245 64-bit 36772) always adds \VC to the end of the path. This was correct operation for VS2015, but incorrect for VS2017 and VS2019. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2021-04-05 15:40:13
|
| [2022-01-20 16:42:00] |
| User217027 - Posts: 5 |
|
Hello, I'm afraid the problem still persists in SC 2347 40792M
|
| [2022-03-06 20:13:57] |
| |
|
We apologize for the delay. We are going to review this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: