1
0
mirror of git://projects.qi-hardware.com/eda-tools.git synced 2024-11-05 04:46:15 +02:00
EDA Tools, Small tools to assist Electronic Design Automation http://projects.qi-hardware.com/index.php/p/eda-tools/
Go to file
2012-01-25 09:40:24 -03:00
boom manu/Makefile: run a recursive make on all subdirectories 2010-10-30 19:12:29 -03:00
dsv dsv/dsv: added option -p to show the path to the file 2011-08-16 13:55:19 -03:00
fab eda-tools/fab/gerb2pbm: convert a Gerber file to a PBM image 2011-06-10 12:38:35 -03:00
fpd2pdf fpd2pdf/fpdoc: ignore items in .pos not defined in the schematics 2011-06-07 16:36:48 -03:00
kicad-cmdline-testing uplevel cmdline patches (entire set won't build right now) 2012-01-11 00:28:19 +01:00
kicad-patches kicad-patches/README: updated for bzr 3378 2012-01-25 09:40:24 -03:00
mlztx mlztx/cptx: new utility for KiCAD board files to copy content across text fields 2011-03-14 13:17:11 -03:00
schhist schhist/schhist2web: > was missing in IMG tag for unchanged.png (vertical bar) 2011-10-01 09:49:31 -03:00
swpcmp swapcmp/: swap (rename) components in a layout 2011-09-29 00:50:52 -03:00
README swapcmp/: swap (rename) components in a layout 2011-09-29 00:50:52 -03:00

eda-tools
=========

This is a collection of utilities for Electronic Design Automation:

- boom: a BOM-processing system. Note that the core scripts of BOOM are
  at http://svn.openmoko.org/trunk/eda/boom. The material here builds
  upon them.

- dsv: data sheet viewer. A simple but efficient system for caching data
  sheets and displaying them with xpdf from command line.

- fpd2pdf: convert a set of footprints (made with FPED) into a
  reviewer-friendly PDF.

- fab: set of tools to convert/generate files for fabrication

- mlztx: set of tools to copy text across layers or across text fields
  in a layout, e.g., to place a version number at several locations

- schhist: a system to walk a KiCad project's git revision history and
  generating Web-browseable graphical differences of the schematics.

- swpcmp: swap components in a layout

Each utility can have its own licensing terms. They're specified in the
respective directory or in the file itself.