9feb13a506134605327c83266c1bafecaf9e20e2 — Karl Schultheisz 3 years ago ccb0ad8 master
1 files changed, 24 insertions(+), 4 deletions(-)

M README.md => README.md +24 -4
@@ 191,7 191,7 @@ are _three_ variables that may appear in footprint library paths:

- KIPRJMOD, pointing to the project directory
- KISYS3DMOD, pointing to global 3D models
- KISYSMOD, pointing to global 3D footprints
- KISYSMOD, pointing to global footprints

It so happens that footprints might be less generic than
symbols. Particularly, connectors such as TRS jacks, and things like

@@ 214,7 214,7 @@ resistor symbol.

# Choosing a component

I've selected a 1% 1 kΩ resistor from Stackpole, part number
I've selected a 1% 1-kΩ resistor from Stackpole, part number


@@ 244,7 244,7 @@ KiCad creates two files:
  newly-added footprint library.

# Associate symbols to footprints
# Associate symbols to footprints... maybe?

When you open Eeschema, it complains:

@@ 395,7 395,7 @@ to celebrate.

	 / \
   > <
	 > <

It's a glencairn glass with a beverage of your choice.

@@ 468,3 468,23 @@ Let's

- rename symbols.lib to local.lib
- move the footprints into a subdirectory

# Cool

At this point, I basically understand what's going on.

- KiCad caches and backs up files because it's pretending to be Git.
  Ignore the caches and backups and check the real files into Git.

- KiCad supports project-specific symbol and footprint libraries; this rocks.
  Because of this feature, it's possible for the user to decide the dependency
  management scheme that works for them, whether it is automatic updates, version
  locking, or vendoring. In addition, version locking can be achieved using Git
  submodules, reducing the need for third-party tooling.

- For non-critical parts of the project, it's OK to use global libraries if
  you're lazy. I highly doubt that the bundled resistor and capacitor symbols
  are going to break my project. However, symbols for diodes, and footprints
  generally, seem to be a greater risk.