Closed santagada closed 2 weeks ago
Does it show Executing command:
in your log file? It should show it before EnvVars exit code: 0
23/09/2024 11:58:05: Executing command: cmd.exe /c call "C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\Tools\VsDevCmd.bat" > nul && "C:/Program Files/PureDevSoftware/10x/10x.exe" -logenv "C:/Temp/10xLogEnvOutput.txt"
the log starts with:
10X_INSTALL_DIR=C:\Program Files\PureDevSoftware\10x\
=::=::\
=C:=C:\Program Files\PureDevSoftware\10x
=ExitCode=00000000
=I:=I:\
<...>
WSLENV=
P4PORT/u:P4IGNORE/u:GG_PROJECT/u:P4WORKROOT/up:GG_USEREMAIL/u:USERDNSDOMAIN/u
_NO_DEBUG_HEAP=1
__DOTNET_ADD_32BIT=1
__DOTNET_PREFERRED_BITNESS=32
__VSCMD_PREINIT_PATH=<...>
then all our env vars (some are confidential)
I'm guessing it doesn't like the multi-line WSLENV var. I'll try it here...
That does seem to be the problem. I'm not even sure how it's possible to set environment variable to be multi-line.
Can you see if this build fixes it: https://www.10xeditor.com/upload/10xVSEnvBatFix.zip
oh YEAH, this fixes it. I was also impressed with it, our team has the gift for these kinds of magic. Thanks for the fix, when this is released I'll delete this build
fix is in early access build (1.0.219)
tested on 1.0.220 and yeah still working perfectly. We also will fix the multi line env var on our side to not trip other tools.
fixed (1.0.230)
After loading my solution and pressing build on the submenu of a project (or anywhere really, tried multiple build all, build file) opens the Build tab with the message: "Build failed. VSEnvBat not setup. Check your 'VisualStudioEnvBat' setting"
But that config is correct and executing the bat file (in default vs2022 professional install) works. I tried increasing the log level of 10x to get more info but this is all that seems to be produced around the pressing of the build on a single project:
here's the spinning building spinner:
Any way to debug this further? We build using nmake command.