kivar_cli: instalation and usage on windows

[honzakutil]

kivar_cli: instalation and usage on windows

[honzakutil]

As I reported in #62, it is possible to install and use kivar cli using pip from the locally created python package.

[markh-de]

I guess that most of the things you've mentioned are not specific to KiVar, but general Python runtime issues on Windows. If I were to use Python on Windows, I'd use WSL (but that's just my personal preference).

Please note that it's not planned to provide the CLI as part of the plugin package. Instead, it will probably be distributed independently via PyPI (pip).

As you mentioned, KiKit does it the same way. First, because KiCad Action Plugins cannot have dependencies (that's a real pity, but I understand how complicated things would get with dependency management). And second, because you don't want to force users into having to run their CLI script from within your KiCad release's plugins directory (or create a symlink to it). There may be even more reasons.

[honzakutil]

I found only one practical example, when I would like to use kicad-cli on windows:

• kivar-cli list --detailed board.kicad_pcb - I really like to see a list of componnets affected by given aspect. This was inspiration fof feature request #38

All other features all accessible via gui, so there is no reason to use kivar-cli during board design process. Two main usecases for kivar-cli I can think of are:

• automated testing of kivar itself
• usage during automated fabrication data generation to set given assembly variant or to check, if current board state is valid

It is likely, that both usecases will use kicad on linux, maybe kicad_auto. Maybe it is not worth the effort to make kivar-cli to run on windows, perfectly.

[markh-de]

Related to #40