templates
/
KiBot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[DOCs] fix typo and add python virtual env support for pcbnew 

Signed-off-by: Yoan Dumas <yoan@eye-lights.fr>
This commit is contained in:
Yoan Dumas 2024-01-21 13:48:52 +01:00
parent c47dcb005b
commit ddd8b06fad
2 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/configuration/quick_start.rst
View File

@ -4,7 +4,7 @@
Quick start Quick start
~~~~~~~~~~~ ~~~~~~~~~~~
If you want to *learn by examples*, or you just want to take a look a If you want to *learn by examples*, or you just want to take a look at
what KiBot can do, you can use the ``--quick-start`` command line what KiBot can do, you can use the ``--quick-start`` command line
option. option.

14
docs/source/installation.rst
View File

@ -144,8 +144,18 @@ Notes about virtualenv
~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~
If you try to use a Python virtual environment you’ll need to find a way 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 the KiCad module (``pcbnew``) available on it. From the `linked
to make it. GitHub issue
<https://github.com/yaqwsx/PcbDraw/issues/119#issuecomment-1274029481>`_
, to make the ``pcbnew`` available on the virtual env, you will need to
run the following command:
.. code:: shell
python -m venv --system-site-packages venv
Then python started in the venv will look at the packages in the system
location, which is where KiCad puts its python code.
In addition: note that the virtual env will change the system share data 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 paths. They will no longer point to things like ``/usr/share/`` but to a