unable to locate vivado.exe

[Sidahmed193]

Describe the bug
teros is unable to locate vivado.exe version 2025.1

Code
hecking Linter configuration (https://terostechnology.github.io/terosHDLdoc/docs/guides/linter)
❌ Some checks failed ❌

---

⊙ Checking linter errors with vivado for VHDL. Current configured installation path: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o -version"
🔎 Searching for the binary "Vivado" in the system path
❌ Vivado not found in the system path. Search executed with: "vivado -version"
👎 The linter installation path is not correctly configured. The binary could not be located in either the system path or the configured path. Please check the documentation.

⊙ Checking linter errors with vivado for Verilog/SV. Current configured installation path: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado.exe -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o\vivado -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o.exe -version"
🔎 Searching for the binary Vivado at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o"
❌ Vivado not found at "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o". Search executed with: "D:\Xilinx\2025.1\Vivado\bin\unwrapped\win64.o -version"
🔎 Searching for the binary "Vivado" in the system path
❌ Vivado not found in the system path. Search executed with: "vivado -version"
👎 The linter installation path is not correctly configured. The binary could not be located in either the system path or the configured path. Please check the documentation.

Please complete the following information:

• OS: [windows 10 22h2]
• VSCode version version [1.105.0]

[hiroshi-ya]

You are not supposed to add the unwrapped executable to Teros's configuration path, because that's not how Vivado on Windows is supposed to be booted. To properly boot Vivado, you have to execute the D:\Xilinx\2025.1\Vivado\bin\vivado.bat.

Unfortunately, putting D:\Xilinx\2025.1\Vivado\bin in the path also won't work because Teros uses the exit code (I think) to determine whether vivado -version is valid, and vivado -version (or vivado.bat -version) exits with 1 instead of 0 on Windows.

Thus, the fix is rather complicated, but I managed to make Teros successfully recognize Vivado. I will probably make a PR for this, but I'm not exactly sure if my "fix" will actually make Teros properly communicate with Vivado. I will have to run more tests.

It's my first day getting in touch with this tool (and npm and typescript), so I'm not sure how long that's gonna take :(