Describe the bug
yosys IS in the path, (in ~/.local/bin) but Teros is not adopting virtualenv, even if it's explicitly set in the Python path setting.
In trying to fix this I found a bug in the path Teros is using for the executable. I tried adding the actual path to the virtualenv where the python part (yowasp-yosys) exists.
I can see that the Project Settings Configuration Check fails to find yosys as it's looking for the wrong thing. It looks for \yosys and /yosys not yosys. i.e. it's expecting to find it in the system root.
This is further proved by setting the Extra Options to /usr2/jasomorg/.local/bin
Looks like the extra options is wrongly used as a path prefix, not a command.
To Reproduce
Edit schematic view config
Set GHDL + Yosys
Set Extra Options PATH=$(realpath -m "$(which python)/..");
result:
Checking Schematic configuration (https://terostechnology.github.io/terosHDLdoc/docs/guides/schematic_viewer/installation)
❌ Some checks failed ❌
*************************************************
⊙ Selected backend: yosys_ghdl with installation path: "".
🔎 Searching for the binary yosys_ghdl at "PATH=$(realpath -m "$(which python)/..");/yosys"
❌ yosys_ghdl not found at "PATH=$(realpath -m "$(which python)/..");/yosys". Search executed with: "PATH=$(realpath -m "$(which python)/..");/yosys --version"
🔎 Searching for the binary yosys_ghdl at "PATH=$(realpath -m "$(which python)/..");/yosys.exe"
❌ yosys_ghdl not found at "PATH=$(realpath -m "$(which python)/..");/yosys.exe". Search executed with: "PATH=$(realpath -m "$(which python)/..");/yosys.exe --version"
🔎 Searching for the binary yosys_ghdl at "PATH=$(realpath -m "$(which python)/..");"
❌ yosys_ghdl not found at "PATH=$(realpath -m "$(which python)/..");". Search executed with: "PATH=$(realpath -m "$(which python)/.."); --version"
🔎 Searching for the binary yosys_ghdl at "PATH=$(realpath -m "$(which python)/..");.exe"
❌ yosys_ghdl not found at "PATH=$(realpath -m "$(which python)/..");.exe". Search executed with: "PATH=$(realpath -m "$(which python)/..");.exe --version"
🔎 Searching for the binary "yosys_ghdl" in the system path
❌ yosys_ghdl not found in the system path. Search executed with: "yosys --version"
👎 The Schematic Backend 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: Ubuntu 22.04.5 LTS
- VSCode version 1.106.3
Screenshots
If applicable, add screenshots to help explain your problem. Share the code as text, not as a screenshots!
Additional context
Add any other context about the problem here.
Describe the bug
yosys IS in the path, (in
~/.local/bin) but Teros is not adopting virtualenv, even if it's explicitly set in the Python path setting.In trying to fix this I found a bug in the path Teros is using for the executable. I tried adding the actual path to the virtualenv where the python part (
yowasp-yosys) exists.I can see that the Project Settings Configuration Check fails to find yosys as it's looking for the wrong thing. It looks for
\yosysand/yosysnotyosys. i.e. it's expecting to find it in the system root.This is further proved by setting the Extra Options to
/usr2/jasomorg/.local/binLooks like the extra options is wrongly used as a path prefix, not a command.
To Reproduce
Edit schematic view config
Set GHDL + Yosys
Set Extra Options
PATH=$(realpath -m "$(which python)/..");result:
Please complete the following information:
Screenshots
If applicable, add screenshots to help explain your problem. Share the code as text, not as a screenshots!
Additional context
Add any other context about the problem here.