Re: Win7 + MSVS2019 fails to create environment....
"Joseph C. Brill" <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <[email protected]> |
The MSVS 2019 batch file VSDevCmd.bat (called via vcvarsall.bat) is attempting to send telemetry information to Microsoft via powershell. As written, VSDevCmd.bat will attempt to send telemetry information via powershell if the environment variable VSCMD_SKIP_SENDTELEMETRY is not defined. This was addressed in SCons v4 by adding the powershell path and the VSCMD_SKIP_SENDTELEMETRY environment variable to the SCons environment. The VSCMD_SKIP_SENDTELEMETRY environment variable suppresses sending the telemetry information. Adding powershell to the path allows the telemetry information to be sent via powershell. If upgrading to SCons v4 is not desired, it may be possible to get around the problem in v3.1.2 by appending the powershell path (e.g., C:\Windows\System32\WindowsPowerShell\v1.0) to the constructed environment path via AppendENVPath in the SConstruct/SConscript file. A less palatable option is to "comment-out" sending the telemetry information directly in VsDevCmd.bat (MSVS2019ROOT\Common7\Tools\VsDevCmd.bat). However, this change could be "lost" after a 2019 update. _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users