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

MOre README tweaks@

This commit is contained in:
John Beard 2018-06-03 15:46:47 +01:00
parent c22676f45c
commit cc06a8ef66
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -6,7 +6,7 @@ can use a Makefile to export your KiCad PCBs just as needed.
For example, it's common that you might want for each board rev:
* Check DRC one last time
* Check DRC one last time (currently not possible)
* Gerbers, drills and drill maps for a fab in their favourite format
* Fab docs for the assembler
* Pick and place files
@ -27,9 +27,10 @@ Set up a virtualenv:
```
virtualenv --python /usr/bin/python2.7 ~/venv/kiplot
source ~/venv/kiplot/bin/activate
```
Install with `pip -e`:
Install `kiplot` with `pip -e`:
```
cd path/to/kiplot
@ -42,7 +43,7 @@ be accessible to the program. You might need to add it to the `PYTHONPATH`.
You might also need to set `LD_LIBRARY_PATH` (you need to be able to load
`libkicad_3dsg.so`).
For example, if you installed in `~/local/kicad`, you might want:
For example, if you installed in `~/local/kicad`, you might have:
```
export PYTHONPATH=~/local/kicad/lib/python2.7/site-packages
@ -53,4 +54,6 @@ export LD_LIBRARY_PATH=~/local/kicad/lib64
There are some things that still need work:
* DRC checking - that can't be done over the Python interface yet.
* DRC checking - that can't be done over the Python interface yet. If/when
this is added to KiCad, KiPlot will be able to also be used for DRC
functional tests instead of a complex additonal test harness in C++.