You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a rather special use case for running TerosHDL and having trouble setting up the toolchain:
As you can see, I am using the SSH feature to connect to a remote server for development and can't simply start VSCode on my Notebook with a customized virtual environment (therefore the use-cases I found on the docs / github do not match :/ ).
Is there any way to "tell" TerosHDL to use a specific Python venv?
I tried this, having success in finding vunit, cocolib and edalize, but for example, I cannot properly set the installation path for GHDL:
Starting a TB results in:
Additional info:
content of "setup_teros_venv.sh" >>
TEROS_DIR="hw/TerosHDL"
PY_CMD=$(which python3)
TEROS_VENV_DIR="${TEROS_DIR}/venv"
$PY_CMD -m venv $TEROS_VENV_DIR && source $TEROS_VENV_DIR/bin/activate && pip install -r $TEROS_DIR/requirements.txt
echo -e "\nConfigure Teros: Click on the Teros icon on the left --> General --> Open Configuration Menu"
echo "For Python3 binary path add the path to the venv folder, e.g.,"
echo -e "$TEROS_VENV_DIR/bin/python3"
Try using the directory path instead of the binary path for GHDL. And
double check that the directory contains the binary.
El mar, 17 sept 2024, 16:18, mkaiser ***@***.***> escribió:
Hi,
I have a rather special use case for running TerosHDL and having trouble setting up the toolchain:
As you can see, I am using the SSH feature to connect to a remote server for development and can't simply start VSCode on my Notebook with a customized virtual environment (therefore the use-cases I found on the docs / github do not match :/ ).
Is there any way to "tell" TerosHDL to use a specific Python venv?
I tried this, having success in finding vunit, cocolib and edalize, but for example, I cannot properly set the installation path for GHDL:
Starting a TB results in:
Additional info:
content of "setup_teros_venv.sh" >>
content of "requirements.txt" >>
The text was updated successfully, but these errors were encountered: