Files
-
hardware / boards / glasgow / glasgow.kicad_pcb
-
hardware / boards / glasgow / glasgow.kicad_sch
-
hardware / boards / glasgow / io_banks.kicad_sch
-
hardware / boards / glasgow / io_buffer.kicad_sch
-
hardware / boards / test-jig / led-board.sch
-
hardware / boards / test-jig / port-connection.sch
-
hardware / boards / test-jig / test-jig.kicad_pcb
-
hardware / boards / test-jig / test-jig.sch
| Filesexamplesout_of_tree | |
|---|---|
| .. | |
| glasgowcontrib | |
| .gitignore | |
| README.md | |
| pyproject.toml |
README.mdExample out-of-tree applet
Most applets currently reside in-tree (within the
glasgowrepository or its forks). On an experimental basis, support for out-of-tree applets is also provided. This feature is considered experimental because the Glasgow software does not provide a stable API.To use this feature, first install the out-of-tree applet. With the recommended method of installation (pipx) this can be done with:
$ pipx inject -e glasgow ./examples/outoftreeOnce installed, the applet is runnable provided a special environment variable is set:
$ export GLASGOWOUTOFTREEAPPLETS=I-am-okay-with-breaking-changes $ glasgow run exampleoot W: g.support.plugin: loading out-of-tree plugin 'glasgowcontrib-applet-exampleoot'; plugin API is currently unstable and subject to change without warning ...Note that there are no
glasgowcontrib/__init__.pyorglasgowcontrib/applet/__init__.pyfiles included. This is intentional;glasgowcontribandglasgowcontrib.appletare PEP 420 namespace packages. Including such an__init__file by mistake will break every other out-of-tree applet, so take care.