From 7f50b3717a5594e2edfb422ac8019c5ce7b4277d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pavel=20H=C3=BCbner?= Date: Tue, 23 Jan 2024 14:33:00 +0100 Subject: [PATCH] CHESTER: Fix Windows SDK installation --- chester/firmware-sdk/installation-on-windows.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chester/firmware-sdk/installation-on-windows.md b/chester/firmware-sdk/installation-on-windows.md index 25ca6e1..feb71ac 100644 --- a/chester/firmware-sdk/installation-on-windows.md +++ b/chester/firmware-sdk/installation-on-windows.md @@ -191,12 +191,12 @@ You can skip this step if you already have **Chocolatey** installed on your syst 1. Activate the **Python** virtual environment: ``` - .\venv\Scripts\Activate.ps1 + .\.venv\Scripts\Activate.ps1 ``` :::caution - When you close the shell (or your text editor with the integrated terminal), you must reactivate the virtual Python environment. Call this command (used in the procedure above): `.\venv\Scripts\Activate.ps1`. In the future, you may have various **West** workspaces with different versions of the **Python** packages, and thanks to the virtual environment concept, these will not suffer from version conflicts. + When you close the shell (or your text editor with the integrated terminal), you must reactivate the virtual Python environment. Call this command (used in the procedure above): `.\.venv\Scripts\Activate.ps1`. In the future, you may have various **West** workspaces with different versions of the **Python** packages, and thanks to the virtual environment concept, these will not suffer from version conflicts. :::