From 38d0790a692399fecf94656ad9efb557821c735f Mon Sep 17 00:00:00 2001 From: "Salvador E. Tropea" Date: Thu, 24 Nov 2022 09:47:31 -0300 Subject: [PATCH] [DOCs] Added more warnings about virtual env use Related to #332 --- README.md | 4 ++++ docs/README.in | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/README.md b/README.md index c6b40ccc..165c74c8 100644 --- a/README.md +++ b/README.md @@ -267,6 +267,10 @@ In this way you can change the code and you won't need to install again. If you try to use a Python virtual environment you'll need to find a way to make the KiCad module (`pcbnew`) available on it. I don't know how to make it. +In addition: note that the virtual env will change the system share data paths. They will no longer point to things like `/usr/share/` +but to a virtual env place. So you'll need to either define environment variables to tell KiBot where are the libs or just add +symlinks from the virtual env to the system level libs. + ### Installation on other targets - Install KiCad 5.1.6 or newer diff --git a/docs/README.in b/docs/README.in index 3a735bb4..1cedf844 100644 --- a/docs/README.in +++ b/docs/README.in @@ -189,6 +189,10 @@ In this way you can change the code and you won't need to install again. If you try to use a Python virtual environment you'll need to find a way to make the KiCad module (`pcbnew`) available on it. I don't know how to make it. +In addition: note that the virtual env will change the system share data paths. They will no longer point to things like `/usr/share/` +but to a virtual env place. So you'll need to either define environment variables to tell KiBot where are the libs or just add +symlinks from the virtual env to the system level libs. + ### Installation on other targets - Install KiCad 5.1.6 or newer